University of TorontoDepartment of Computer ScienceCSC340S - Information Systems Analysis and DesignMarch 14, 2003 John MylopoulosAssignment 3: Detailed Design for an Information SystemDue Date: 12:00midnight Friday April 11, 2003This assignment counts for 15% of the final gradeThis assignment is to be undertaken by students working in teams of three. Teams of two will beallowed when no third member is available.The AssignmentThe objective of the assignment is to give you practice in doing a detailed design for theinformation system you have been working on for assignments 1 and 2. The detailed designshould include selecting hardware, networking and software for the new system, designing aglobal architecture, proposing a detailed software architecture, also defining a relational databaseschema and suitable I/O procedures and interfaces.Directions: This assignment consists of eight steps:1. Adopt the requirements specification of assignment 2. You may want to revise it on thebasis of the comments you received from the marker.2. Define a global system architecture, consisting of computer networks (existing or new),hardware (existing or new) and software platform (operating system, other commercialsoftware you will be using for your system).3. Select hardware, software and networking to be purchased for the new system. Specifyclearly the criteria and alternatives you are using for your decision.4. Propose a software architecture for the new system and justify your choice.5. Based on the general design you have proposed, design the database schema for thedatabase component of your system. Take into account workloads in proposing arelational database schema. Use both class diagrams and ER diagrams to describe thecontents of your database before you generate a relational schema.6. Design I/O procedures and user interfaces.7. Do a detailed design of the classes that are part of your system using class, interactionand state diagrams.8. Write a report that describes the complete system design. The report should include as anappendix the requirements specification on which your design was based, along with acareful account of how all requirements (functional and non-functional) were addressedin your proposed design.What to Hand InPlease submit your assignment electronically by the assignment deadline by visiting the CDFelectronic submission system at http://www.cdf.toronto.edu/students/submit.html. Also hand in ahardcopy to the instructor’s office on Friday April 11, or on Monday April 14.There is no limit on the length of the report that you have to hand in. It is suggested however,that you turn in a report of reasonable length, sufficient to convince the marker that you havedone a good job, without boring him/her.CSC340S Asst3 – Information System DesignDetailed Marking SchemeMarker:Team:_____________________________________________________Total Marks:______________/101Marks for this assignment depend on the factors listed below.A: Global Architecture (20%). Description and justification ofthe hardware, networking and software platform selected for thedesign; also, description and justification of the softwarearchitecture adopted.Value 20 marks: _______• Specification of the computer network (existing or new) ( ) insufficient ( ) partially sufficient ( ) adequate• Specification of the hardware (existing or new)( ) insufficient ( ) partially sufficient ( ) adequate• Specification of the software platform (operating system andother commercial software you will be using for your system)( ) insufficient ( ) partially sufficient ( ) adequate• Specification of the software architecture, for example,client-server, MVC, layered, etc( ) insufficient ( ) partially sufficient ( ) adequate• Identification of sub-systems and major components( ) insufficient ( ) partially sufficient ( ) adequate• Justification that the overall design meets all requirements ( ) insufficient ( ) partially sufficient ( ) adequateB: Program Design (21%). A description of the detaileddesign of the application component of the system, given interms of class, sequence, and state diagrams. Value: 21 marks: ______B1. Class Diagrams (7%)Value: 7 marks: ______• (Informal) Description of class diagrams, including a datadictionary.( ) insufficient ( ) partially sufficient ( ) adequate• Quality of the diagrams( ) Little understanding of class diagrams.( ) Some understanding, but there are serious flaws oromissions.( ) Reasonable diagrams, but not enough to capture thedesign of the application and/or there is missing informationfrom some diagrams, e.g., attributes, operations,multiplicities( ) Good and complete diagrams, cover pretty well thedesign( ) Excellent work• Justification that the design meets relevant requirements( ) insufficient ( ) partially sufficient ( ) adequateB2. Sequence Diagrams (7%)Value: 7 marks: ______• (Informal) Description of sequence diagrams.( ) insufficient ( ) partially sufficient ( ) adequate• A description derived from the data dictionary was included.( ) yes ( ) no• Quality of the diagrams( ) Little understanding of sequence diagrams.( ) Some understanding, but there are serious flaws oromissions.( ) Reasonable diagrams, but not enough to capture the designof the application and/or there is missing information fromsome diagrams, e.g., conditional branching or terminations( ) Good and complete diagrams, cover pretty well thedesign( ) Excellent work• Justification that the design meets relevant requirements( ) insufficient ( ) partially sufficient ( ) adequateB3. Statechart Diagrams (7%)Value: 7 marks: ______• (Informal) Description of statechart diagrams.( ) insufficient ( ) partially sufficient ( ) adequate• A description derived from the data dictionary was included.( ) yes ( ) no• Quality of the diagrams( ) Little understanding of statechart diagrams.( ) Some understanding, but there are serious flaws oromissions.( ) Reasonable diagrams, but not enough to capture the designof the application and/or there is missing information fromsome diagrams, e.g., events, conditions and actions for varioustransitions( ) Good and complete diagrams, cover pretty well thedesign( ) Excellent work• Justification that the design
View Full Document