CS220 Project System Design 28 February 2004 Remember to submit your system analysis report Project Supervisor: Timothy Au Email: email@example.com URL: www.geocities.com/timothykfau/pj
System Development Schedule The following is a suggested system development schedule for CS220 Project: * The above schedule could be adjusted according to the actual condition of individual groups.
System Development Schedule The course requires • Project Demonstration • Prepare Demonstration (20.Jun ~ 2.Jul..2004 ) • Planning and Work Distribution • Equipment Acquisition • Environment Setup • Software Installation and Configuration • Rehearsal • Demonstration (3.Jul.2004) • Final Documentation • Preparing Final Documentation (ongoing) • Final Checking Final Documentation ( 5.Jun.2004) • Submission (10.Jul.2004)
Documentation • System Design Report • Cover letter • Cover page and/or title page of the project • Confidentiality, Distribution Control, Revision History • Table of contents • Executive summary • Introduction • Description of the new systems (15 marks) • Narrative (5 marks) • Illustrations supporting narrative (5 marks) – any kind of system overview, system flow, high level functional hierarchy business case, … that help to elaborate textual description of the new system. • Process Flows (5 marks)
Documentation • Detailed Design (40 marks) • Data Design (10 marks) • Architectural Design (10 marks) • Procedural Design (10 marks) • Interface Design (10 marks) • Hardware and Software Selection (5 marks) • Explanation / Justification of development and implementation hardware and software equipment (5 marks)
Documentation • Description of the new systems (15 marks) • Narrative (5 marks) • Illustrations supporting narrative (5 marks) • Process Flows (5 marks)
Documentation • Description of the new systems (15 marks) • This section is concerned with a detailed description of the system as it will be[whereas the description of the current system is concerned with a detailed description of the system as it is.] • Narrative (5 marks) • Supported by diagram,charts, tables etc. • Examples of diagrams presented include system breakdown, organization charts indicating roles and responsibilities. • Items of information presented in the narrative should include inputs, outputs and processes. • Illustrations supporting narrative (5 marks) • any kind of system overview, system flow, high level functional hierarchy business case, … that help to elaborate textual description of the new system. [ Narrative + illustration = 5 pages]
Documentation • Description of the new systems (15 marks) • Process Flow • Details Process Flow Diagram – Leveled Data Flow Diagrams (DFDs) of adequate depth i.e. up at least 2nd DFD (see note below). • Normally, the Context Diagram and the 1st Level DFD are placed in the main document; with the 2nd level or beyond in the appendix.[Detailed Process Flow = 3 pages + appendix] • Note:- • Context Diagram = Level 0 (1 single page) • First Level DFD = Level 1 (World Atlas containing 7 +/- 2 bubbles match those inputs and outputs of the context diagram; 1 page) • Second Level = Level 2DFD (Breakdown of each of the above 7 +/- 2 bubbles; i.e. 7 +/- 2 pages) • Third Level = Level 3 DFD (Further breakdown of the above level; n x 7 +/- 2 pages!)
Documentation • Detailed Design (40 marks) • This section should contain the following FOUR aspects of design: • Data Design (10 marks) • Key design representations like data dictionary, entity relationship diagram, with associated supporting explanations. • Detailed representations (e.g. data element dictionary) should be placed in the appendix. [Data Design = 4 pages + appendix] • Architectural Design (10 marks) • Program structure information should be presented here. • For example, breakdown of a system into sub-component parts and modules associated explanation, control relationships and information exchange between modules [such as Structure Chart or HIPO Chart].[Architectural Design = 4 pages + appendix]
Documentation • Detailed Design (Continued) • Procedural Design (10 marks) • Based on the program structure, procedural information for each module should be presented here. • The procedural information presented here can be based on pseudo-code or flowcharting techniques. • Project groups should take note that this section is not a blind listing of procedural code – the detailed procedure code should be put in the appendix with only the key procedural details (and supporting explanations) in the main document.[Procedural Design = 4 pages + appendix] • Interface Design (10 marks) • Screen design information should be presented here • Project group should clearly distinguish screen layout and the actual screen. • All too often, project groups have presented pages of screen captures in this section without really understanding that these screen captures must be preceded by a section explaining the design of the screens. • Representation like screen layout (e.g. why menu bar or icon is being used in this particular system, colour scheme, font sizes) similar to that of SD206 should be elaborated. • The emphasis in this section should be correct and rational justification of screen layout and design; and notthe volume of screen capture presented! • The main document here should only include the key template(s) of all screen s are derived from; with the detailed or specific templates in the appendix. [Interface Design = 4 pages + appendix]
Documentation • Hardware and Software Selection (5 marks) • Explanation / Justification of development and implementation hardware and software equipment (5 marks) • Here, the following TWO aspects should be presented: • Development hardware and software equipment • An explanation of the equipment that would be used to develop the software portion of the system. • Again, explanation and justification is required for the equipment proposed. • Implementation (Production) hardware and software equipment • An explanation of the equipment that users would need to possibly acquire in order to make use of the completed system. • Some explanation and justification is necessary for the equipment proposed. • A simple itemized list without elaboration SHOULD NOT awarded any marks. • [Hardware and Software Selection = 4 pages] • In the real world, we should include the product specification, white papers, product advantages against others alternatives.
Techniques, Tools & Platforms [CS220 Project Initiation Slide# 4] • Analysis: • UML • Class Diagram • Interaction Diagrams • Sequence Diagram • Collaboration Diagram • Activity Diagram • State Diagram • Structured Analysis • Context Diagram • Data Flow Diagram (Level 0 DFD) • Process Specification / Structured English / Narrative / Mini-specification • Structure Chart • Decision Tree / Table • Data Dictionary
Techniques, Tools & Platforms [CS220 Project Initiation Slide# 5] • Design: • UML • Class Diagram Refined • Sequence Diagram Elaborated • Component Diagram • Structured Design • Detailed Data Flow Diagram (Level 1 & Level 2) • Prototyping • In the real world, you should actually consider the following • In-house development • Prototyping (Incremental and Throw-away) • Purchase Software Package or Customized Software Package (CSP) • Outsourcing • RAD / JAD / RUP / MSF • See Also CS220 Project Initiation Slide# 7-8
A Reminder on Project Ideas and Tools • Project Ideas • Please refer to CS220 Project Briefing Slide# 20 • Project Tools • SHOULD NOT [ADCS CS220 Student Manual p.11 Project tools Sec. 2] [CS220 Project Briefing Slide# 21] • Program code generator • Dreamwaver, Front Page [It does not mention the specific names explicitly] • Internet Projects • Examples: • A system that run mainly on the Internet (e.g. on-line purchasing system for DVD shop) • A system that still run on a local machine with Web front-end graphical user interface.
Tasks for last two weeks • Project Initiation • Plan your project, schedule project meeting and breakdown tasks, distribution of work. • Submit your Project Proposal • Keep track your project and prepare a biweekly Progress Report • Analysis Phase: • Requirement gathering: Fact finding - interviewing, prepare questionnaires, … • Conduct analysis: DFD, Structure Chart,… • Prepare your System Analysis Documentation. • Keep track your project and prepare a biweekly Progress Report
Tasks for next couple of weeks • Design Phase • You should arrange your team meeting. Keep track your project and prepare a biweekly Progress Report • Breakdown tasks and subtasks. • Design Task A • Design Task B • Prepare your System Design Documentation. • Book your consultation sessions on Saturday 13.Mar.2004 and 03.Apr.2004 * First-Come-First-Serve (* 27.Mar.2004 will be rescheduled to 03.Apr.2004) • You should submit your System Design Documentation for First Review either office counter (hardcopy) OR email to me at firstname.lastname@example.org (softcopy, preferred) on Saturday 13 March, 2004 and for Second Review on Saturday 27 March, 2004 . • The final submission System Design Documentation is Saturday 17 April, 2004.NOTE: CHANGE OF FINAL SUBMISSION DESIGN DOCUMENT Saturday 8 May, 2004 • The next lecture Saturday 17 April, 2004 you will learn about system development and implementation. NOTE: NEXT LECTURE Saturday 8 May, 2004
Q & A Any Question? • See your group on Saturday 13.Mar.2004 and 03.Apr.2004 for group consultation. • See you ALL on Saturday 8 May, 2004(instead of Saturday 17.Apr. 2004)for the lecture on System Development and Implementation. Note • Hurry up with your system analysis documentation and submission if you haven’t done so. • Proceed on your system design phase and documentation. • Deadline of Booking Project Demonstration (tentatively, Saturday 26 June 2004) • Project Demonstration (tentatively, Saturday 3 July 2004) • Deadline for submission of Final Project Documentation (tentatively, Saturday 10 July 2004) Thank you! Project Supervisor: Timothy Au Email: email@example.com URL: www.geocities.com/timothykfau/pj