HANOI UNIVERSITY

Faculty of Information Technology

----------&----------

SYSTEM ANALYSIS AND DESIGN

ACTIVITIES REPORT

Module name: System Analysis and Design

Year: Fall 2019
Instructor: Trịnh Bảo Ngọc
Topic: HANU’s Educational Management System
Group: Active Service Provider Network (ASPNET)
Group members:
- Đỗ Hải Bình (1801040022) – 3C18, SAD01
- Nguyễn Công Quang (1607020094) – 2N16, SAD01
- Đỗ Minh Tâm (1701040154) – 2C17, SAD02
- Nguyễn Phương Anh Việt (1701040186) – 2C17, SAD02

1
 Table of Contents

ABSTRACT................................................................................................................................. 3
1. Business Modelling.................................................................................................................... 5
2. Requirements Definition............................................................................................................ 6
3. Prototype.................................................................................................................................. 7
4. Analysis & Design..................................................................................................................... 8
5. Conclusion.............................................................................................................................. 11

2
 ABSTRACT
Education has long been an indispensable part of life. The wild rise of worldwide population has
put much stress on the educational system, making it harder to efficiently manage. Hanoi
University (HANU) is no exception. Each year, the number of students enrolling in the university
increases substantially, which requires the university to employ an effective means of educational
management to deal with a huge amount of information. HANU’s New Educational Management
System is a promising solution to existing problems within the current educational management
system of the university regarding course registration, course management, staff management,
student management, tuition fee management and so on. In this project, we, members of Active
Service Provider Network (ASPNET) aim to use Rational Unified Process (RUP) as a guideline
to analyze the business context, to capture and accurately specify system requirements, to create
architecture design and data design for the Educational Management System. Our system is
designed in such a way to fulfill both functional requirements and non-functional requirements.
The output of our works includes documents from three processes: Business Modelling,
Requirements Definition and Analysis & Design, along with Unified Modelling Language (UML)
model artifacts of the system in both Visual Paradigm format and JPEG format, and a runnable
prototype of the system.

3
 GROUP ROLES

Members Roles
Software Architect, Architecture Designer,
Đỗ Hải Bình (1801040022)
Prototype
Nguyễn Công Quang (1607020094) Requirements Modeller
Đỗ Minh Tâm (1701040154) Data Modeller
Nguyễn Phương Anh Việt
Business Modeller, Business Process Analyst
(1701040186)

Since this project is the final project of this SAD course, all members cooperate in most of the
processes; especially in heavyweight processes as Use-Case specification during Requirement
Definition, and Use-Case realization during Analysis & Design.

4
1. Business Modelling
Việt is responsible for business modelling and business process analyzing, however he does not
do every work himself. He made a detailed analysis of the target organization (Hanoi
University), by describing the workflow of one or several business use-cases, along with
defining the responsibilities, operations, attributes, and relationships of one or several business
workers and business entities. Quang and Bình assisted him in outlining supplementary
specifications of the business. Việt led and coordinated business use-case modelling by
determining the business actors, business processes and use-cases, along with outlining how the
actors conduct the processes within the target organization.

5
2. Requirements Definition
Requirements Definition includes writing a number of documents along with identifying and
specifying the use-cases. Quang directed the team in this process, and he wrote the Stakeholder
Requests document. Tâm helped Quang outline a top-level view of system use-cases inside
Software Requirements Specification document. Quang and Bình co-operated in writing the
Vision document of the project, Bình and Việt specified the Requirements Management Plan,
and Bình himself provided the project’s Supplementary Specifications. Quang divided the use-
case specifications among the team so that everybody could experience the work of modelling
actual business processes to system use-cases. Bình dealt with use-cases related to Student actor,
Quang specified Administrator use-cases, Việt documented use-case specifications for the actor
Moderator and Tâm outlined specifications for use-cases that are applicable for both registered
and unregistered users.

6
3. Prototype
Bình is responsible for the implementation of a working prototype to demonstrate the
functionalities of HANU’s New Educational Management System. The prototype is based on
pure HTML/CSS/JavaScript with no additional libraries, providing a simple working Graphical
User Interface for the system functionalities specified in Requirements Definition, such as Log
in, Create Course, Add/Delete/Modify Course Registrations …
The sole purpose of the prototype is to demonstrate the system functionalities without any sort of
server or persistent data. Additionally, the prototype only presents the views of the system, and
does not represent the MVC architecture.
Accounts for testing the prototype:

Username Password Account Type

student student Student
admin admin Administrator
moderator moderator Moderator

7
4. Analysis & Design
As a novice software architect, Bình was the one responsible for architecture-related activities
and artifacts throughout the project. He constructed the overall structure of each architectural
view, the decomposition of the views, and how the components are grouped together. He has a
breadth view of the system architecture. The table below describes in details the activities that
were conducted to design software architecture in the Analysis & Design workflow.

Activity Description Output Artifacts

Prioritize Use  Define input to the selection of the set of Software Architecture
Cases scenarios and use cases that are to be Document
analyzed in the current iteration.
 Define the set of scenarios and use cases that
represent some significant, central
functionality.
 Define the set of scenarios and use cases that
have a substantial architectural coverage or
that stress or illustrate a specific, delicate
point of the architecture.
Architectural  Define a candidate architecture for the Use-Case Realization
Analysis system, based on experience gained from Specifications,
similar systems or in similar problem Deployment Model,
domains. Software Architecture
 Define the architectural patterns, key Document, Design
mechanisms and modeling conventions for Model
the system.
 Define the reuse strategy.

Identify Design  Refine the analysis mechanisms into design Design Model,
Mechanisms mechanisms based on the constraints imposed Software Architecture
by the implementation environment. Document
Incorporate  Analyze the interactions of analysis classes Design Model,
Existing Design to find design classes. Software Architecture
Elements  Refine the architecture, incorporating reuse Document

8
 where possible.
 Identify common solutions to commonly
encountered design problems.
 Include architecturally significant design
model elements in the Logical View section
of the Software Architecture Document.
Describe  Describe how the functionality of the system Software Architecture
Distribution is distributed across physical nodes. Document,
Deployment Model
Identify Design  Analyze interactions of analysis classes to Design Model
Elements identify design model elements.

Bình was also responsible for the system design process, during which the responsibilities,
operations and attributes of the classes, along with the relationships between them are defined.
He also adjusted the classes to fit with Model-View-Controller architecture and the actual
implementation of Hanoi University’s New Educational Management System. He did not deal
with all the Use-Case Realization Specification documents by himself, however. He divided the
work among the group so that every member writes the Use-Case Realizations corresponding to
the Use-Case Specifications the member was assigned by Quang. The following table outlines
his activities as a system designer in the Analysis & Design process.

Activity Description Output

Use-Case  Identify the classes which perform a use Analysis classes, Use-
Analysis case’s flow of events. Case Realization,
 Distribute the use case behavior to those Design Model, Analysis
classes, using use-case realizations. Model
 Identify the responsibilities, attributes and
associations of the classes.
 Note the usage of architectural
mechanisms.
Use-Case  Refine use-case realizations in terms of Use-Case Realization
Design interactions.
 Refine requirements on the operations of

9
 design classes.
Class Design  Ensure that the class provides the behavior Design Classes,
required by the use-case realizations. Updates to Design
 Ensure that sufficient information is provided Model.
to unambiguously implement the class.
 Handle non-functional requirements related
to the class.
 Incorporate the design mechanisms used by
the class.

As a database designer, Tâm was responsible of defining the tables, indexes, views, keys,
constraints and other database-specific attributes necessary to store, retrieve, update and delete
persistent objects. The following table describes his activities as a Data Modeller in the Analysis
& Design process.

Activity Description Output

Database Design
 Ensure that persistent data is stored Data Model
consistently and efficiently.

 Define behavior that must be implemented in

the database and the database management
system.

10
5. Conclusion
Based on the knowledge acquired from this course (FIT5SAD), along with other courses before
and during the Fall 2019 semester, we have designed an Educational Management System that
more or less meets real-world business requirements. In our project, we have modelled the
business processes and mapped them to system requirements using in both textual form and
UML graphical form. Our group has also created a system design based on Model-View-
Controller architecture so as to improve reusability of system components. A runnable prototype
of the system was also built based on the captured requirements to demonstrate system
functionalities. However, the output of this project can still be further improved. As third-year
university students who have limited experience in software projects and System Analysis &
Design, mistakes in our work are inevitable, but we are still able to deliver a product that we can
be satisfied with. ASPNET members will continue to improve our knowledge to deliver better
products in the future.

11