1. 1 SA Capstone Requirements and Design Week 1 SYST36367 Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso

2. 2 Lesson Objectives F System Vision F Existing System Description F Project Proposal F Client Presentations F Group Meetings

3. 3 System Vision F Before starting detailed Systems Analysis activities, a System Vision document is very helpful to:  Determine whether a Systems Request merits further investigation  Summarize the justification for a system F The System Vision document should:  Summarize the motivations, scope and benefits of a proposed system  Allow readers to decide whether the system warrants a more detailed examination  Entice interested individuals to continue reading related documents  Serve as the basis for an “elevator pitch” to quickly and effectively inform partners/investors about the merits of the project

4. Systems Analysis and Design in a Changing World, 6th Edition 4 Identify the Problem System Vision Document Problem Description What is the problem and idea for the solution? System Capabilities What are the capabilities the new system will have? Helps define the scope Business Benefits The benefits that accrue to the organization Tangible (in dollars) and intangible benefits

5. 5 System Vision Document RMO CSMS

6. 6 RMO CSMS Vision Document (1)

7. Systems Analysis and Design in a Changing World, 6th Edition 7 RMO CSMS Vision Document (2)

8. 8 RMO CSMS Vision Document (3)

9. 9 Existing System Description- Fact Finding  To understand the existing system, your group should perform some Fact Finding which includes:  Interviewing various stakeholders  Collecting and analyzing system artifacts  Possibly observing users and/or surveying them  Drawing a Context Diagram of the system

10. 10 Existing System Description- Artifacts  Request and collect artifacts to better understand the current business processes  Sample artifacts include: u Purchase Orders u Invoices u Reports u Instruction Manuals u Training Materials u Current system software or simulation of this software u Basically all documentation that they have or use relative for doing their business

11. 11 Existing System Description – Context Diagram  Remember that there are only four symbols in DFDs: u External Entity (source or sink of data) u Process u Data Flow u Data Stores (not used in a Context Diagram!)  Remember that at least one end of the Data Flow must be connected to a Process!

12. 12 Data Flow Diagrams DFD Symbols *From: Systems Analysis and Design, Ninth Edition, Gary B. Shelly & Harry J. Rosenblatt, Course Technology, CENGAGE Learning, 2012

13. 13 Existing System Description – Context Diagram  In Class Exercise

14. 14 Narrative  After completing the existing system’s Fact Finding your group should be in a good position to write a Narrative to describe the project.  This Narrative can serve as an excellent starting point for subsequent analysis and design activities

15. 15 Reminder – Capstone Project Proposal  Your Capstone Project Proposal is due in two weeks!Capstone Project Proposal  This means that for the next two weeks you must: 1.Choose a Capstone group to work with for the remainder of semester 5 and all of semester 6! 2.Select a Capstone Project 3.Complete your Capstone Proposal  One key part of the Capstone Proposal is the System Vision  Remember that your proposal and project should look beyond a single customer’s current needs

16. 16 Client Presentations  Here’s a great opportunity to find about some potential Capstone projects!  More client presentations may be scheduled for the next class.

17. 17 Group Meetings  Please break into your groups to get started on selecting a Capstone Project and/or planning the first deliverable.  If you do not have a group then use this time to form a group. Remember to choose your group wisely as your group will be expected to work together for all of the 5 th and 6 th semesters!