UML design
Referencing Styles : Harvard | Pages : 32
Specification The Case Study Student attendance register (SAR) system for the CIS Department The Department of Computing and Information Systems (CIS) at the University of Greenwich (UoG) operates an intranet to support its core academic operations. Various subsystems on the CIS Intranet have read-only access to parts of the main UoG Academic Information System (AIS) which deals centrally with student registration, finances and progression You have been asked to develop a system to record student attendance to teaching sessions. A teaching session can be a Lecture, a Tutorial session or a Lab session. Each session is associated with a lead member of staff and a room, lecture theatre or lab section. Courses run over periods of 13 or 26 weeks, following a set pattern. The system should allow a course coordinator to maintain lists of students associated with the course, assign them into one of multiple lecture occurrences and into smaller tutorial/lab groups associated to tutors and rooms/labs. The list of students comes from the central AIS system that records all students registered on a course. Each student is uniquely identified by their Student ID (SID). The course coordinator can add other students to the register list. These are students who are attending the course but they have not yet registered officially to the course. These must be centrally registered UoG students to a valid programme for CIS and they are identified by their SID or their unique computer systems user ID, also maintained centrally within the AIS. These students will be attached to the course as “temporary registrations”. Once the student registers officially to the course, their inclusion into the register lists for the course will automatically become “permanent”. Tutors on the course can print blank registers for the current week for their own sessions. Students sign next to their name on the list during the teaching session. Following this the tutor will enter the student attendance onto the system by entering a “tick” next to each attending student’s name for that session. During some lecture sessions, a lecturer can pass around the class a customised PDA with an integral barcode reader. Attending students will scan their student card barcode using the reader to record their attendance at the session. Following this, the lecturer will dock the PDA at a cradle at the school office that will record all attendances onto the register system. The system also provides individual attendance records and attendance statistics to tutors, managers and admin staff within the school. Students can only see their own attendance record by logging onto the system. Finally, the system should provide a hyperlinked version of a register with links to other information on each system coming from the central AIS system, such as registration status, holds, student photograph, programme name and a list of courses the student is officially registered on. You are part of a system development team to do the analysis, design and development of their new hybrid system. They have a tight deadline of 4 months for the system to go live, staff should be trained within 2 weeks and the analysis, design and development of the new system should be within the budget of 40,000 pounds as decided by the Vice Chancellor. You are required (individually) to model the current business system and propose a new, integrated software SAR system that will include all current functionality and enhancements needed. Your job is to elicit the exact requirements from the client (your tutors). This can be done in Q and A sessions during class and on the MOODLE discussion forum. However, you will (as good software engineers) confirm in writing any assumptions and conclusions you make from these discussions. For example, assumptions and conclusion can also be made about the different stakeholders and any conflict of interest they may face. THIS SHOULD BE DONE VIA the discussion forum. In this way everyone will have access to all the assumptions, and you will have a confirmation from the teaching team. The report must include the following: Part 1: Your software house decided to design and build the system using object-oriented methodologies, in order to allow for more flexible design/build iterations and re-use of design and code. You have therefore now been asked to produce the design of the new system using object-oriented design principles and UML. The UML design should follow the analysis documentation produced in CW1 by providing an in-depth ULM design for the SAR. Your report should therefore include the following: Your team need to do the following tasks: • As a first task, you need to discuss within the team the first draft solution. Based on feedback received for your first coursework, it is probable that modifications to you initial design is necessary. The team meetings should be minuted. 1. A UML Use Case diagram (a revised version of the one included in SDP Coursework 1) – A UML Use Case diagram identifying all actors and the Use Cases they are involved with. 2. Interaction Diagrams. Using UML sequence (interaction) diagrams perform an analysis of all main Use Case scenarios (first level use cases) – at least 3. 3. State chart diagrams. One diagram for each major class (at least 3). 4. Design UML Class Diagrams – Show the attributes, all methods and associations for all classes. The design class diagram should also reflect any design patterns that you considered to use. Part 2 Your team is required to build a working prototype of SAR system. The prototype should only simulate a mobile application. The prototype should reflect the following: 1. It should be built in an Object Oriented way using any appropriate technology you are familiar with (The prototype can be built as a .NET application (desktop or web), as a Java stand-alone application or any other application you are familiar with). 2. The prototype system should have enough business and UI functionality to test the business life cycle of the main use cases from your use case diagram. Only at a later stage, after the prototype is approved, a full system app would be required by the client. A well designed prototype code could be used straight for the final app using dedicated cross platform development suites such Xamarin. The finished product app is out of this coursework scope and you are not required to create one. I will need to demonstrate this system to the tutor , I have to be able to add all the code to my computer and run successfully so teacher can mark my work ,also need set of instruction on how to add this system to Java Compiler .. Net beans or any . I have attach Original Coursework requirements marked in red in world doc and PDF doc is a ready made Attendance Register System for you use as an example . Also if Possible I will need first draft for download to present to the tutor so he can see my progress ..it should include at least : 1. A UML Use Case diagram (a revised version of the one included in SDP Coursework 1) – A UML Use Case diagram identifying all actors and the Use Cases they are involved with. 2. Interaction Diagrams. Using UML sequence (interaction) diagrams perform an analysis of all main Use Case scenarios (first level use cases) – at least 3. 3. State chart diagrams. One diagram for each major class (at least 3). 4. Design UML Class Diagrams – Show the attributes, all methods and associations for all classes. The design class diagram should also reflect any design patterns that you considered to use. Contact me for .if you have any quotations I applied for your service again ..in hope for a good price ,as other service send me quote for 200 pounds which is to high for me .