MIS 2000 Class 19 System Development Process Updated 2018

1. MIS 2000 Class 19 System Development Process Updated 2018

2. Outline • System Development Process • System Planning • System Analysis & Design • System Construction, Installation, Testing • System Deployment & Maintenance • Good System Design

3. System Development Process • Plaining what organizational goals an IS needs to meet; • also the economic side of IS (costs, benefits) • Analyzing business processes and data As-is and as To-be; an As-is system usually have problems • Designing system solutions to problems in processes & data; How to implement To-be system * • Making the system physically; programming, purchasing software & hardware • Putting software on hardware + check how it works; a reality check (testing the quality of work in earlier phases) • Rolling a system out to users and fine-tuning it while being used 1 Plan System • Conduct • System • Analysis 3 Design System 4 Construct System 5 Install & Test System • Deploy & Maintain System

4. System Development Process -Waterfall Logic 0 Plan System X • System development steps can be run on the entire system sequentially in defined periods. • Linear, finish one step, move to the next. • If development time is longer, system may be obsolete at time of release. Conduct System Analysis Design System 1 Construct System Install & Test System 2 Deploy & Maintain System years

5. Newer methodologies of systems development tend • be faster: • developing a system in smaller parts • each part developed quickly • testing the developed piece and move to the next • Same development activities repeated (as in Waterfall) on system parts and usually several times on each part.

6. Check Point 1: Answer Questions Below • Put the number next to a phase name to show the correct waterfall methodology: ___ design ___ construct ___ install and test ___ analyze ___ plan ___ deploy and maintain 2. Match each definition with the numbered phase in question 1: • Implementing a To-be system. ___ • Giving a system to users and ensuring that it functions properly. ___ • Analyzing the As-is business processes and data and their To-be state. ___ • Identify characteristics of the Waterfall and Rapid methodology (write W or R next to a concept): Developing system piece by piece ( ); Developing system phase by phase ( ); Repeating development activities ( ); Each system part developed quickly ( ); Risk of building an obsolete system ( ); Better control of time period for system development ( ).

7. Plan System • Business goals and plans to be accomplished with new system: • Optimize process design (CCCF aspects) • Improve process performance (CVCT & CCCF aspects) • Define new processes • What are the costs and financial returns expected from the process/IS changes? • How does IS in planning can help to accomplish goals above? Your IS IS you need

8. Perform System Analysis • The goal is to understand the existing (present) business and systems (As-is) in order to envision improvements (To-be system). • Focus on the present and future: • Analysis of present organizational processes (design, performance) and what can be improved - interview end-users & managers. • Analysis of present data and what else is needed (business documents like reports, communications) • Analysis of IT in the existing system and possible improvements • Result: System requirements – defining what new IS should deliver Analyze business, data & IT/IS Define System Requirements

9. Design System • How will system requirements be realized • Creating a new IS or upgrading the present IS; still just on “paper”. • The data model is created or changed in case of upgrade. • The processing of data in the system is defined according to the model of organizational process resulting from System Analysis. • User Interface is designed (content and look of screens, & their sequence). STUDENT database

10. Construct System • A system is physically made based on the design created (data diagrams, and process diagrams that determine what software should do – how the data should be processed). • Options for acquiring software & hardware: • Write application software (computer programs) • Buy application software (off-the-shelf software) • Rent application software • Purchase computers and other hardware Paired rather than individual programming is often practiced today as part of rapid IS development.

11. Install & Test System • Installation: Setting up a system into operation stage. Software is mounted on hardware, etc. • Testing: Evaluating the performance of a developed system. • Kinds of tests run based on moving from small to large : • Unit testing (system part, by experts) • System testing (whole system, by experts) • Acceptance testing (whole system, by users)

12. System Deployment Methods • Direct deployment - New system completely replaces old one - Higher risk, lower cost • Parallel deployment • Old and new system used until the new proves reliable • Lower risk, higher cost time OLD IS OLD IS NEW IS NEW IS Old out/New in time Old out New in

13. Maintain System in Production Stage • As IS is used and managed, its development continues in small - this is the system maintenance domain. • System maintenance includes: • De-bugging software • IS modifications based on business needs (e.g., enlarging data storage) • Adding new software and hardware driven by vendors

14. Check Point 2: Answer Questions Below 4. Match the concepts on the left to those on the right by filling the blank column with appropriate numbers. 5. What is user interface and which aspects of it do system developers focus on?

15. Good System Design A well-designed IS system needs to: • Do the work it is planned to support – fit with business processes • Be easy to learn and use - user interface quality, menu design: • intuitive screen items (labels, buttons; see MS Office screens below) • screens reasonably complex (ERPS can be very complex) • letting users know where they are (navigation aspect; avoiding duplication of menu items across screens; avoid deep menus/provide tips) • allows for easy tracking and correction of errors • Support efficient work - user interface & technical aspects. Impacts on process performance (timing, costs). Drop-down menu design Current designs: Drop-down vs. Tabs

16. Good design is goal but this might happen…  1 2 But… 3

17. Good design is goal but this might happen…  1 2 3

18. Check Point 3: Answer Questions Below • Look the Web pages below and compare them. Are there any design issues? http://umanitoba.ca/faculties/management/programs/undergraduate/index.html http://umanitoba.ca/faculties/management/

19. S u m m a r y • System development process takes activities of planning, analysis, designing, constructing, installing, testing, and deploying, and maintaining an IS. • Structural and newer rapid methodologies. • Plan for new IS can aim at optimizing process design, improving process performance, and creating new processes. • System Analysis focuses on both business and existing IS (if any) to understand how work is done and how it should be. System design creates new functions, data model, user interface. • IS construction implements IS design physically. • There are 3 methods of IS testing and 2 basic deployment strategies. • System maintenance continues throughout the system use period. • Well-designed IS performs work needed, is easy to learn and use, and enables efficient work.