learning%20%20 port
TRANSCRIPT
LearningPortCmsSoftware Architecture
Project Code: Learningportcms
Document Code: Learningportcms_Architecture_Design_v1.1
20-Mar-2015
Internal use
Center Management System - Software Architecture Design
v1.1
RECORD OF CHANGE
*A - Added M - Modified D - Deleted
Effective Date Changed Items A*
M, D
Change Description New Version
Package A Define software for designing
package Learningportcms.UI
1.1
Internal use
Center Management System - Software Architecture Design
v1.1
SIGNATURE PAGE
ORIGINATOR: Jyothi 20-03-2015
Developer
REVIEWERS:
APPROVAL:
Internal use
Center Management System - Software Architecture Design
v1.1
TABLE OF CONTENTS
1 INTRODUCTION................................................................................. . . . . . . . . . . . . . . . 6
1.1 Purpose......................................................................... . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Scope.............................................................................. . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Definit ions, Acronyms and Abbreviat ions ....................... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 ARCHITECTURAL REPRESENTATION .............................................. . . . . . . . . . . . . . . . . . 8
3 ARCHITECTURAL GOALS AND CONSTRAINTS ................................... . . . . . . . . . . . . . . . 8
4 USE-CASE VIEW ............................................................................... . . . . . . . . . . . . . . . 9
4.1 Use-Case Realizations............................................... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 LOGICAL VIEW .............................................................................................. . 11
5.1 Overview............................................................................... . . . . . . . . . . . . . . . . . . 11
5.2 Flow Diagram.......................................................................................... . 12
5.2.1Login... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.2.2Manage Center and Staff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2.3Finance... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2.4Student.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2.5Report Use case... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.3 Architectural ly Signif icant Design Packages .......................... . . . . . . . . . . . . . . . . . . . . . 17
2.1Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3 Screen Requirement ..................................................................... . . . . . . . . . . . 21
Internal use
Center Management System - Software Architecture Design
v1.1
1 INTRODUCTION
This section describes the purpose and the scope of this document. Also the
definit ions, acronyms and abbreviat ions used in this document are described in this
section. The last two parts of this section contain references and an overview of the
entire document.
1.1 Purpose
This document is the result of the architecture design phase for the Center
Management System project. The architecture of the Center Management System
includes its logical and physical structure which has been forged by all the strategic
and tactical decisions applied during development.
This document provides a comprehensive architectural overview of the system, using
a number of different architectural views to depict different aspects of the system. It
is intended to capture and convey the signif icant architectural decisions that have
been made on the system.
This document is intended to be read by all members of the project.
1.2 Scope
This Software Architecture Document provides an architectural overview of the
Center Management System. The Center Management System is being developed by
Learning Port to maintain the different centers along with student registrations.
This document is divided into the following sections:
• Architectural representat ion
Internal use
Center Management System - Software Architecture Design
v1.1
• Architectural goals and constraints
• Use-Case view
• Logical view
• Process View
• Deployment View
1.3 Definitions, Acronyms and Abbreviations
Terminology Explanation
ADD The Architectural Design Document (this document), the high
level design document for the entire system.
URD The User Requirements Document, records the users’
requirements for the system.
Internal use
Center Management System - Software Architecture Design
v1.12 ARCHITECTURAL REPRESENTATION
In the Architecture Representation contains 4 Views:
• Use-Case Views
• Logical View
• Process View
• Deployment View
3 ARCHITECTURAL GOALS AND CONSTRAINTS
This architecture is implemented 3-iter architecture, and contains framework which
integrated the Web API in the .Net framework 4.5. It can be customized for reuse.
Internal use
Center Management System - Software Architecture Design
v1.1
4 USE-CASE VIEW
In this system, so many use cases are there. Here are some important use cases:
1. Login and Authenticate:
When user login to the system, system will authenticate user and identify user’s
roles.
2. Display User Menu List:
System connects to the DB to retr ieve User Menu list based on user role. The Menu
List module is used to manage user task list.
3. Finance :
System has to capture Subject Fee, Centers Fee and Vouchers taken by Center
Operators along with effective date and Expiry date.
System has to able to key in discount by vouchers, number of Months and number of
subjects.
4. Registration:
The Authenticated user clicks on one menu in user’s Menu list to view the menu
details. When user clicks on Student to register new student, after f i l l ing some
information user clicks on register. The system connects to DB, and save the student
details in the CMS database and LMS database.
Internal use
Center Management System - Software Architecture Design
v1.1
5. Enrollment:
The authenticated user use this function
There are main functions in Enrollment Menu:
• Check the Voucher balance: User has to check the Voucher balance
before doing Enrollment.
• Select Student: User can select the student to Enroll
• Select Courses: The system retrieves a list of course offerings from
LMS system and display the list. User selects the courses and process
the enrollment and collects money from Student.
• LMS access: Once enrol lment is done send the related data to LMS
database Through Web API and as well as save in our CMS database.
Student can login to LMS and retrieve related course details.
6. Report:
The Center Head User prints report of the system. System use .NET framework 4.5 to
generate the report, detail base on the input which was retrieved from a table in DB.
Internal use
Center Management System - Software Architecture Design
v1.1
4.1 Use-Case Realizations
Here is the system use case.
5 LOGICAL VIEW
5.1 Overview
The document is divided into the following sections:
Internal use
Center Management System - Software Architecture Design
v1.1
• Flow Diagram
• Architecturally Signif icant Design Packages
• Structuring using Layer Architecture Pattern
5.2 Flow Diagram
5.2.1 Login
Internal use
Center Management System - Software Architecture Design
v1.1
5.2.2 Manage Center and Staff
5.2.3 Finance
Internal use
Center Management System - Software Architecture Design
v1.1
5.2.4 Student
5.2.4.1 Registrat ion
Internal use
Center Management System - Software Architecture Design
v1.1
5.3 Architecturally Significant Design Packages
2.1 Overview
There are 4 packages in this application which separate to 3 parts:
• Presentation
• Business Object
• Data Access.
Internal use
Center Management System - Software Architecture Design
v1.1
Below are four packages in this application:
No Package name Descript ion
01 Learningportcms.BusinessObject It contains all business
objects which are used
in this application. And
the source code which
is generated will be
input in this package.
02 Learningportcms.Uti l i t ies It contains all common
function that wil l be
used in this
applicat ion.
03 Learningportcms.DAL It contains some
classes that defines all
methods to connect to
database for
updating/getting data.
04 Learningportcms.UI It contains aspx pages,
JavaScript f i les,
images, …
Internal use
Center Management System - Software Architecture Design
v1.1
Presentation layer is your user interface layer where you can design your interface
using html web controls or windows controls or mobile controls. It can be your
website or windows applicat ion or mobile applicat ion.This layer only communicates
with business layer.
Applicat ion layer or Business Layer is the middle layer or bridge layer that connects
Internal use
Center Management System - Software Architecture Design
v1.1
database layer and presentation layer. In this layer you can write your business logic
(logic written as per business requirement) or any validat ion code.This layer
communicates with database layer and presentation layer.
Database layer which makes the connection to the database server. In this layer you
can write database connection and sql queries or stored procedures. This layer only
communicates with business layer.
When user post any data from from user interface (presentation page), data first goes
to the business layer there data will be validated then validated data is posted to
database layer to insert into the database.
When user request any data from the database then the request is f irst processed by
the business layer validates the request and sends to database layer then database
layer forwards it to the database server and fetches necessary records. Found
records are loaded by the database layer and passes it back to the business layer
then business layer passes those records to the presentation layer.
5.3 Screen Requirement
5.3.1. Staff Management
5.3.1.1 Role
Internal use
Center Management System - Software Architecture Design
v1.1
5.3.2. Finance Management
5.3.2.1 Subject Fee
Internal use