sheridancollege.ca sa capstone requirements and design week 1 1
TRANSCRIPT
sheridancollege.ca
• System Vision• Existing System Description• Project Proposal• Group Meetings
LESSON OBJECTIVES
2
sheridancollege.ca
• Before starting detailed Systems Analysis activities, a System Vision document is very helpful to:
Confirm that the Systems Request merits further investigation and development Summarize the justification for a system
• 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
SYSTEM VISION
3
sheridancollege.ca
– 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• What are the benefits that accrue to the organization?• Can they be expressed in Tangible (monetary) and
intangible benefits (non-monetary) terms?
IDENTIFY THE PROBLEM
sheridancollege.ca
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
EXISTING SYSTEM DESCRIPTION- FACT FINDING
14
sheridancollege.ca
Request and collect artifacts to better understand the current business processes
Sample artifacts include:• Purchase Orders• Invoices• Reports• Instruction Manuals• Training Materials• Current system software or simulation of this software• Basically all documentation that they have or use
relative for doing their business
EXISTING SYSTEM DESCRIPTION- ARTIFACTS
15
sheridancollege.ca
Remember that there are only four symbols in DFDs:
• External Entity (source or sink of data)• Process• Data Flow • Data Stores (not used in a Context Diagram!)
Remember that at least one end of the Data Flow must be connected to a Process!
EXISTING SYSTEM DESCRIPTION – CONTEXT DIAGRAM
16
17
Data Flow DiagramsDFD Symbols
*From: Systems Analysis and Design, Ninth Edition, Gary B. Shelly & Harry J. Rosenblatt, Course Technology, CENGAGE Learning, 2012
sheridancollege.ca
In Class Exercise
EXISTING SYSTEM DESCRIPTION – CONTEXT DIAGRAM
20
sheridancollege.ca
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
NARRATIVE
21
22
Reminder – Capstone Project Proposal
Your Capstone Project Proposal is due in two weeks! This means that for the next two weeks you must:
1. Spend time with your client to gather all the information required.
2. 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.
sheridancollege.ca
Please break into your groups to start on your planning for the first deliverable.
GROUP MEETINGS
23