Higher Nationals in Computing
Unit 30: Application Development
ASSIGNMENT 1
Learner’s name: TRANQUOCTAN
ID: GCS18462
Class: GCS0703B
Subject ID: 1670
Assessor name: PHAN MINH TAM
Assignment due: Assignment submitted:
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
COMPUTING 5 Unit 30: Application Development ASSIGNMENT 1, Assignments of Computer Networks
1.3 Overview The Software Design Document is divided into 10 sections with various subsections. Thesections of the Software Design Document are: 1. Introduction 2. System Overview 3. System Architecture 4. Software Requirement Specifications 5. Software Interface Design 6. Component Design 7. Class Diagram 8. Data Design 9. Risks 10. References 2 System Overview This system can be used to manage trainee accounts, manage trainers, manage course categories, manage courses, manage topics, assign topic to course, assign trainer to topic, assign trainee to course. This is a system used by HR department. We have three roles inthissystem, an administrator, training staff and a trainer. 3 System Architecture The system will work with ASP.NET MVC 5. ASP.NET MVC 5 is a framework that implements the Model-View-Controller (MVC) architecturepattern. MVC is an architecture pattern that stands for Model-View-Controller. Model The Model component corresponds to all the data-related logic that the user
Typology: Assignments
2022/2023
1 / 42
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download COMPUTING 5 Unit 30: Application Development ASSIGNMENT 1 and more Assignments Computer Networks in PDF only on Docsity!
Higher Nationals in Computing
Unit 30: Application Development
ASSIGNMENT 1
Learner’s name: TRAN QUOC TAN
ID: GCS
Class: GCS0703B
Subject ID: 1670
Assessor name: PHAN MINH TAM
Assignment due: Assignment submitted:
ASSIGNMENT 1 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing
Unit number and title Unit 30: Application Development
Submission date Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Tran Quoc Tan Student ID GCS
Class GCS0703B Assessor name Phan Minh Tam
Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice.
Student’s signature
Grading grid P1 P2 P3 M1 M2 D
ASSIGNMENT 1 BRIEF
Qualification BTEC Level 5 HND Diploma in Computing
Unit number Unit 30: Application Development
Assignment title Analysis and Design solution for a given problem
Academic Year 2020
Unit Tutor TamPM
Issue date Submission date
Submission Format:
Submissions include 3 documents:
- A software design document in PDF format. Writing must be professional.
- An evaluation document in PDF format. Writing must be professional.
- A presentation document in Powerpoint format.
Assignment Brief and Guidance:
Scenario : As the technology is being developed rapidly nowadays, FPT Co. desires to build the continuing study environment throughout the corporation. It is necessary to develop a system, which manages the activity of “Training” for internal training program of the company. This system can be used to manage trainee accounts, manage trainers, manage course categories, manage courses, manage topics, assign topic to course, assign trainer to topic, assign trainee to course. This is a system used by HR department. We have three roles in this system, an administrator, training staff and a trainer. The detailed description of those roles can be viewed in the attached document (Requirements.docx).
Tasks You and your team need to prepare a software design document with the following sections: A requirement specification which explores the problem by a set of user and system requirements, as well as determine any risks related to the successful completion of your application. You are advised to use an SRS template or modify one to complete this task. An evaluation section in which you research the use of software development tools and techniques and identify any that have been selected for the development of this application. You should compare them and justify your choices.
A design section in which you use chosen tools from previous step to produce design diagrams for your solution based on the requirement specification.
Your team also needs to present your work based on this documents.
Learning Outcomes and Assessment Criteria
Pass Merit Distinction
LO1 Produce a Software Design Document by analyzing a business-related problem and deduce an appropriate solution including a set of initial requirements LO1 & 2 D1 Justify the tools and techniques chosen to realize a custom built website. Justify your preferred selection of tools and techniques in deducing an appropriate solution to a business related problem.
P1 Explore a business-related problem and produce a well- defined Problem Definition Statement supported by a set of user and system requirements.
P2 Determine any areas of risk related to the successful completion of your application.
M1 Analyze a business- related problem using appropriate methods and produce a well-structured Software Design Document that defines a proposed solution and includes relevant details on requirements, system analysis, system design, coding, testing and implementation.
LO2 Use design and development methodologies with tools and techniques associated with the creation of a business application
P3 Research the use of software development tools and techniques and identify any that have been selected for the
M2 Compare the differences between the various software development tools and techniques researched
Table of content
- Unit 30: Application DevelopmentASSIGNMENT 1..........................................................................
- 1 Introduction..................................................................................................................................
- 1.1 Purpose...............................................................................................................................
- 1.2 Scope..................................................................................................................................
- 1.3 Overview.............................................................................................................................
- 3 System Architecture......................................................................................................................
- 4 Software Requirement Specifications..........................................................................................
- 4.1 Use case diagram..............................................................................................................
- 4.2 Use case specification.......................................................................................................
- 5 Software Interface Design..........................................................................................................
- 5.1 Wireframe.........................................................................................................................
- 5.2 Web page in a tree...........................................................................................................
- 6 Component Design......................................................................................................................
- 6.1 Sequence diagram............................................................................................................
- 6.2 Activities diagram.............................................................................................................
- 7 Class Diagram..............................................................................................................................
- 8 Data Design.................................................................................................................................
- 8.1 Data descriptions..............................................................................................................
- 8.3 Database diagram.............................................................................................................
- 8.4 Data dictionary.................................................................................................................
- 9 Risks............................................................................................................................................
- 10 References................................................................................................................................
1 Introduction
The project is to build the continuing study environment throughout the FPT corporation. Develop a system which manages the activity of “Training” for internal training program of the FPT company.
This design document presents the designs used or intended to be used in implementing the
project. The designs described, follow the requirements specified in the Software
Requirements Specifications document prepared for the project.
1.1 Purpose
The purpose of this document is to present a detailed description of the designs of the Internal Training System, created for the FPT company. The Software Design Document provides information necessary to provide description of the details for the software and system to be built.
1.2 Scope
This document gives a detailed description of the software architecture of the Training system. This Software Design Document is for a base level system which will work as a proof of concept for the use of building a system the provides a base level of functionality to show feasibility for large scale production use. It also displays some of the use cases that had transformed into sequential and activity diagrams.
1.3 Overview
The Software Design Document is divided into 10 sections with various subsections. The sections of the Software Design Document are:
- Introduction
- System Overview
- System Architecture
The View component is used for all the UI logic of the application. For example, the Customer view will include all the UI components such as text boxes, dropdowns, etc. that the final user interacts with.
Controller
Controllers act as an interface between Model and View components to process all the business logic and incoming requests, manipulate data using the Model component and interact with the Views to render the final output. For example, the Customer controller will handle all the interactions and inputs from the Customer View and update the database using the Customer Model. The same controller will be used to view the Customer data.
ASP.NET supports three major development models: Web Pages, Web Forms and MVC (Model View Controller). ASP.NET MVC framework is a lightweight, highly testable presentation framework that is integrated with the existing ASP.NET features, such as master pages, authentication, etc. Within .NET, this framework is defined in the System.Web.Mvc assembly. The latest version of the MVC Framework is 5.0. We use Visual Studio to create ASP.NET MVC applications which can be added as a template in Visual Studio.
4 Software Requirement Specifications
4.1 Use case diagram
Administrators
Trainer
Training Staff
Basic Flow 1. User enter username and password
- Validate username and password
- User access to the system
Alternative Flow No
Use case name Create account
Use case description Administrator create new user account or training staff create new trainee account
Actors Administrator, training staff
Pre-Conditions Account haven’t created before
Account permissions is valid
Post-Conditions Account has been created
Basic Flow 1. User log in to system
- User click Create button in page
- User input username, password and role
- User create account successfully
Alternative Flow No
Use case name View course
Use case description Trainer view their course
Actors Trainer
Pre-Conditions Trainer already have their account
Account permissions is valid
Post-Conditions Trainer’s course show in their screen
Basic Flow 1. User log in to system
- User click View Course button in page
- User view course successfully
Alternative Flow No
Use case name Assign
Use case description Assign username/password, assign trainee/topic to course, assign course to course categories or assign trainer to topic
Actors Administrator, Training Staff
Pre-Conditions Account available
Account permissions is valid
Post-Conditions Assign successfully
Basic Flow 1. User log in to system
- User click Assign button in page
- User chose which object to assign
- User click Submit button
Alternative Flow No
Basic Flow 1. User log in to system
- User click Update button in page
- User input information they want to update
- User click Submit button
- Update successfully
Alternative Flow No
Use case name Delete
Use case description User want to delete account, delete course or course category
Actors Administrator, Training Staff
Pre-Conditions Account available
Account permissions is valid
Post-Conditions Account has been deleted
Basic Flow 1. User log in to system
- User click Delete button in page
- User chose which object to delete
- User click Submit button 5.Delete successfully
Alternative Flow No
5 Software Interface Design
5.1 Wireframe
Login Page
Admin Manage Page
Trainer Page
Trainer Update Profile
Main Page
Add Topic