150 likes | 274 Views
Systems Analysis And Design MIST 4620. Fall 2002 Professor: Dale Goodhue. Business Challenges. Management. Information Technology. Business Processes. Business. Solutions. Organization. The Systems Design Life Cycle. Project Identification and Selection Initiation and Planning.
E N D
Systems Analysis And Design MIST 4620 Fall 2002 Professor: Dale Goodhue
Business Challenges Management Information Technology Business Processes Business Solutions Organization
The Systems Design Life Cycle Project Identification and Selection Initiation and Planning Analysis Gathering Info Process Modeling Data Modeling Design System, Architecture Interface, Data Storage Program Implementation Construction Testing Installation
The Systems Design Life Cycle Project Identification and Selection Initiation and Planning Ch 2,3 Ch 4-7 Events, DFDs, ERDs, Logical DBs Analysis Gathering Info Process Modeling Data Modeling Ch 8-13 Logic Modeling, Prog Design, Forms, Interfaces, Physical DBs, Design System, Architecture Interface, Data Storage Program Ch 14-15 Coding, Testing, Training, Change Mgmt Implementation Construction Testing Installation
Interpersonal Skills Analytical Skills Management Skills Technical Skills Skills Needed During The Systems Design Life Cycle Project Identification and Selection Initiation and Planning Analysis Gathering Info Process Modeling Data Modeling Design System, Architecture Interface, Data Storage Program Implementation Construction Testing Installation
Request Budget Availability Issue Purchase Department Budget/Acct Order Bud Commit Information Available Notification Vendors of receipt P.O. Vendor Bill of Lading Information Receive Vendor Goods P.O. Signed BoL Open P.O. R. of G. P.O. File Expenditure Invoice Receipt of R. of G. Make Goods File Check Payment A High Level Data Flow Diagram of the Purchasing Process
Department Notification Department of receipt Receive Bill of Goods Vendor Lading Signed Bill of Lading R. of G. Receipt of Goods File
Department Budget/Acct Information Vendor Expenditure Open P.O. P.O. File Invoice Receipt of Make R. of G. Check Goods File Payment
Deliverable #1, Sept 18 engagement letter System Profile --Business Context --Problem or Opportunity --Proposed Solution --Hoped-for Benefits Initial Scope Chosen and why project roles and timeline fact finding techniques presentation 1 (3 Slides Only!) Deliverable #2, Oct 18 data flow diagrams entity relationship diag. event table pseudo-code (selected) presentation 2. Deliverable #3, Dec 9 prototype user manual dialogue diagram screen layouts/report design costs and benefits recommendation presentation 3
Presentations for Deliverable 1 Consider this a presentation to your customer, in which you hope to convince them that there is a business reason to do a first level analysis and prototype development project. You have 12 minutes and 4 slides! Your presentation should include (not necessarily in this order): The Business Context (with numbers!) What business is this? How big? Who are their customers, competitors, challenges, strategic niche? Business Problem or Opportunity. (What is the problem or opportunity that your system will address?) What decision will the system make, based on what external info and what internal info? Proposed Solution and Hoped-for Benefits Remember: In a real situation, you are asking the customer to put up real dollars (and real management time) to pursue this possible system. Convince them this is worth it!
Consider that you will be presenting for an internal review in your own consulting firm. We will critique your work and make suggestions for improvements. (Strongly) Suggested Components for Presentation 2 Quick summary of the business context (with numbers!), the business problem,and the proposed solution and benefits. Context diagram of proposed solution. Event Table. Must correspond to the context diagram and the Level 0. Level 0 DFD. Must correspond to the event table. Level 1 DFDs for the key events. Data Stores must correspond to ERD. ERD with attributes indicated (even if just listed to the side of entities). Tell us the extent to which you are automating versus reengineering. Hand out to the class: ERD; Level 0 DFD; Level 1 DFD for the most interesting events.
(Strongly) Suggested Components for Presentation 3 Quick summary of the business context (with numbers!), the business problem,and the proposed solution and benefits Level 0 DFD for system, events to be prototyped highlighted. Description of the prototype to be demonstrated (supporting a subset of the major events) Demonstrate the prototype (make it interesting; tell a story) Discussion of the costs and benefits of this system. (Be hard nosed make some estimate of the benefits (hard and soft). If it doesn’t look worth the cost, say so. Recommendation to the client. Hand out to the class: screen image of Data Model (from Access); Level 0 and level 1 DFD for most interesting event that you prototyped. You DO need to turn in: executive summary(!), individual journals, user manual (so literate person could operate your prototype), etc. You Don’t need to turn in: user manual overview, how to get help
Gearing Up for the Project Go to the course web site: http://www.terry.uga.edu/~dgoodhue/mist4620.htm Explore a bit. What can you find there? Download the Project Description and Deliverables Download the Team Contract and Code of Contact Read them! Team Contract and Code of Conduct are Due Aug 28
Required for Friday August 23 Determine Group Membership (Group Name?) List on a clean sheet: names, in alphabetical order Identify potential project sites Set time of meeting for Team Contract We will take team photos (stand in alphabetical order)