SA Capstone Requirements and Design Week 1 SYST

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

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

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 3

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

System Vision Document RMO CSMS 5

RMO CSMS Vision Document (1) 6

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

RMO CSMS Vision Document (3) 8

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 9

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 10

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

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

Existing System Description – Context Diagram Ø In Class Exercise 13

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 14

Reminder – Capstone Project Proposal § Your Capstone Project Proposal is due in two weeks! § This means that for the next two weeks you must: 1. 2. 3. § § Choose a Capstone group to work with for the remainder of semester 5 and all of semester 6! Select a Capstone Project 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 15

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

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! 17