1 / 15

Business Systems Integration

Business Systems Integration. An Overview. Evolution of BSI - beginnings. It came from Java – MIS 225. It became C# – MIS 400. Evolution – [Before]. Taught best practices in application development Application development using different exercises in book Web services in week 5

breena
Download Presentation

Business Systems Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Business Systems Integration An Overview

  2. Evolution of BSI - beginnings It came from Java – MIS 225 It became C# – MIS 400

  3. Evolution – [Before] • Taught best practices in application development • Application development using different exercises in book • Web services in week 5 • Final project: canned from text books • Present project to instructor

  4. Evolution – [After] Analysis Req’ts Definition Design Dvlpmnt Implmnt

  5. Evolution of Systems Integration • Replacement of Fourth Gen Languages (MIS 225) • An programming class using Java • Began as a C# programming class • Book: Microsoft # Professional Projects • Objective: to learn OOP • Web services by mid-term • Added components • Final Project • Presentation • Added refinements by using a single business model that builds upon itself • In-class: SouthBreezeGroceries • Assignments: YourSpace • Modified projects to introduce inter-dependencies • Standalone client websites  Order tracking system • Shifted emphasis: Coding  Coding + Analysis + Communication • Reduced coding by replacing HW with SbS • Simulated actual client, with some built in flexibility for user interface • Invited professionals from outside the class

  6. Course Objectives in Syllabus • Integrate technology skills learned in earlier courses to provide effective solutions for business problems. Specifically: • Learn to work with VWDE, in the technical development environment of the CoB. • Learn to develop basic logic and code structures using C# • Understand usage of web controls to develop graphically appealing and usable web applications. • Be able to develop applications that require applications that run custom database queries. • Be able to use, understand, and develop web services, and understand their advantages. • Demonstrate effective and practical use of Systems Analysis and Design by using the SDLC problem based learning methodology • Analyze project charge and identify business problems and requirements of project. • Evaluate problems, issues, risks and potential solutions, identify optimal solutions in light of those • Designand develop system description documents, such as use case diagrams, process flow diagrams, entity relationship diagrams, site maps, etc. • Create prototypes of user interface, and proposed functionality. • Evaluate how the proposed project provides an effective solution. • Employ Agile Computing Methodology to develop complex technical solutions. 3. Develop proficient communication, collaboration and presentation skills • Communicate effectively to collect project information and establish project scope. • Create content with appropriate coverage, accuracy and level of detail for a client. • Present content with proper clarity, organization, professionalism in appearance, and presentation time management. • Use visual aids and supplements effectively. • Communicate and collaborate in and across system teams.

  7. Business System Integration

  8. Solutions of Step-by-step directions *** Individual techniques listed after Table of contents in the MIS 400 book

  9. Skills of Step-by Step directions • SbSes show exactly how to do something • Example: adding columns to a GridView • Contain breakdowns to introduce new techniques • SbSes test application of what was shown earlier • by using Fill-in-the-blanks for repeated techniques • SbSes build complex applications by building upon themselves • E.g. CustomerRegistrationExecuteNonQueryWebservice.aspx

  10. Course Components

  11. Business Systems Integration Technical Development 2. GUI Page Creation 3. Code Structures 1. SQL Systems Analysis & Design 4. Methods 4. GUI Data Controls 5. Data Control in Code Communications

More Related