This document is expected to be edited and keep involving throughout the sign progress to make the design closer and more balanced to most stakeholders’ needs. Introduction Purpose The major function of the design specification document is to define and describe the system design and architecture. The progress of developing and implementing the system will be faster for the software development team with a clear understanding of design and architecture of the system.
Intended audience Software development team Implementation team Prerequisite documents Requirement specification document Goals The design model presented in this document is expected to be able to achieve the allowing goals. To allow user to Hadley the system well and access different functionality special training. 2. To allow administrator to grab information and use administrative function. 3. To provide a platform for students and professors communicate with each other. 4. To display the information provided by the department clearly that students can receive. . To prevent student missing any promoting or planned events or activities held or promoted by the department. Glossary ML (Unified Modeling Language): An approved ISO standard general purpose modeling language in the field of software engineering to provide a standard way to visualize the design of a system. Class diagram: A type of structuralize programmers describes the structure of a system by showing the system’s classes, their attributes, operations/ methods, and the relationship among objects.
Sequence diagram: An interaction diagram that shows how processes operate with one another and in w hat order. It is a construct of a Message Sequence Chart and it shows object interactions arranged in time sequence, also depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to array out the functionality of the scenario. Overview of this document System overview: A class diagram for the whole system will be shown to describe the overall structure of the system.
System Design: Several use cases are created according to different objectives, basically different functions. For each use case, class diagram and sequence diagram are provided to show the detail of the design. Screen layout for users and report layout for administrators are also simulated and drawn to briefly show how the system will to showing to end users. System overview The “Innovator” stakeholder management system can be divided into several major features and functions as follow: Newsletter Social Network (forum) 3. Calendar 4.
Use Case (Research World) (User can search, view, comment through the Research World feature. ) 9. Report Layout The system administrator can view the “Data Record” page. It will show the activities of all users. Including all the post on forum, comment on research, modify of company information etc. System Administrator can add / edit / delete all content on the system (Home page, with log in feature. ) (Admit can check the daily activities of all the users. ) (System Admit can view the sponsors and helpers of each event. )