CSC555 (Software Engineering)
Computer Inventory System
CSC555 Report Guidelines
Report Format :
1) Font Style Arial Size 11
2) Paragraph Justify and line spacing 1.5
3) Each chapter must start with new page
4) Each page must be numbered bottom page centered and line above.
5) Each page must have header, left side –Subject Code & name and
System Name, Right side – Semester. line below
6) Cover page use the template given below……..
Mac-Jun 2012
CSC555 (Software Engineering)
Computer Inventory System
Mac-Jun 2012
Bachelor of Computational Mathematic,
Faculty of Computer & Mathematical
Sciences
UiTM Terengganu
Project Report
NAME OF YOUR SYSTEM
Course Code
Course Name
Semester
Lecturer Name
Student ID
: CSC555
: Software Engineering
: Mac – Jun 2012
: Mohd Hanapi Abdul Latif
Student Name
CSC555 (Software Engineering)
Computer Inventory System
Mac-Jun 2012
TABLE OF CONTENTS
1
2
3
4
5
6
Introduction
2
1.1 Introduction to subject .................................................................................................... 2
1.2 Introduction to organization ............................................................................................ 2
Background .................................................................................................................... 2
Objective ........................................................................................................................ 2
Mission ........................................................................................................................... 2
1.3 Organizational chart ....................................................................................................... 2
1.4 Project team background ............................................................................................... 2
System Planning
3
2.1 Requirement analysis ..................................................................................................... 3
Objective of the system .................................................................................................. 3
Scope of the system ....................................................................................................... 3
2.2 Current system overview ................................................................................................ 3
2.3 Proposed system overview ............................................................................................ 3
2.4 Functional Requirement ................................................................................................. 3
2.5 Timeline schedule .......................................................................................................... 3
System analysis
4
3.1 Introduction ..................................................................................................................... 4
3.2 Diagram and Descriptions .............................................................................................. 4
3.2.1 Functional Modeling With Use Case Diagram ............................................................... 4
3.2.2 Functional Modeling With Activity Diagram .................................................................... 4
System Design
5
4.1 Introduction ..................................................................................................................... 5
4.2 Physical design .............................................................................................................. 5
System diagram ............................................................................................................. 5
4.3 Database design ............................................................................................................ 5
Entity Relationship Diagram (ERD) ................................................................................ 5
Relational Schema ......................................................................................................... 6
Data Dictionary ............................................................................................................... 6
4.4 User Interface Design .................................................................................................... 6
Interface flow for Student ............................................................................................... 6
Login Page Student ........................................................................................................ 7
Implementation
8
5.1 Introduction ..................................................................................................................... 8
5.2 Tools use ........................................................................................................................ 8
Hardware ........................................................................................................................ 8
Software ......................................................................................................................... 8
5.3 Coding phase ................................................................................................................. 8
5.4 Testing phase ................................................................................................................. 8
Unit testing ..................................................................................................................... 8
Integration and module testing ....................................................................................... 9
Conclusion
9
1
CSC555 (Software Engineering)
Computer Inventory System
1
Mac-Jun 2012
Introduction
1.1
Introduction to subject
<TBA>
1.2
Introduction to organization
Background
<TBA>
Objective
<TBA>
Mission
<TBA>
1.3
Organizational chart
<TBA>
1.4
Project team background
The project team consists of four members. The following are the list of the
members.
Name:
Post
: Project Manager
Main Responsibility :
The project manager is responsible for ensuring that the project is completed on
time and within budget and that the system delivers all benefits that were intend
by the project sponsor.
<TBA>
2
CSC555 (Software Engineering)
Computer Inventory System
2
Mac-Jun 2012
System Planning
2.1
Requirement analysis
Objective of the system
<TBA>
Scope of the system
The scope of the system are:
<TBA>
2.2
Current system overview
<TBA>
2.3
Proposed system overview
<TBA>
2.4
Functional Requirement
2.5
Timeline schedule
Project has been develop and manage carefully to meet the time allocated to
our team which is 4 months. For that purpose Gantt chart has been used to
plan the progress of the project.
<TBA>
3
CSC555 (Software Engineering)
Computer Inventory System
3
Mac-Jun 2012
System analysis
3.1
Introduction
During the analysis stage, the project goals are transformed into defined
functions and operation of the intended application. Below are how we analyzes
end-user information needs to come out with the new system.
3.2
Diagram and Descriptions
The following has been identified:
i.
Actors
Three major actors were identified.
a. Student of FTMSK
b. <TBA>
ii.
Use Cases
Nine main use cases were identified
<TBA>
3.2.1 Functional Modeling With Use Case Diagram
<TBA>
3.2.2 Functional Modeling With Activity Diagram
<TBA>
4
CSC555 (Software Engineering)
Computer Inventory System
4
Mac-Jun 2012
System Design
4.1
Introduction
The purpose of the design phase is to decide how to build it. The major activity
that takes place during the design phase is evolving the set of analysis
representations into design representations. Throughout the design phase, the
project team carefully considers the new system in respect to the current
environment and systems that exist within the organization as a whole.
4.2
Physical design
System diagram
Figure 1
4.3
Database design
Considering the amount of data that will be stored in the database and future
expansion of the size of the data will grow, the developer team has decided
to use relational database management system (RDBMS) using Microsoft
SQL application as the database application for the system developed.
Entity Relationship Diagram (ERD)
<TBA>
5
CSC555 (Software Engineering)
Computer Inventory System
Mac-Jun 2012
Relational Schema
<TBA>
Data Dictionary
Table Name: COURSE
Description: To store course offered information
Column Name
courseCode
courseName
Description
To store course code
To store courset
name
courseDesc
To store course
description
courseCreditHour To store
contact/credit hour
coursePreReq
To store course
prerequire
4.4
User Interface Design
Interface flow for Student
6
Data Type Remarks
varchar2(6) PK
Varchar2(12)
Varchar2(40)
Int(2)
Int(6)
Reference:
‘COURSE’
CSC555 (Software Engineering)
Computer Inventory System
Mac-Jun 2012
Login Page Student
7
CSC555 (Software Engineering)
Computer Inventory System
5
Mac-Jun 2012
Implementation
5.1
Introduction
This phase was started after all data was collected and system is clear in our
picture with the assisting of the design documentation. The system was
developed by using three types of software; Macromedia Dreamweaver and
PHP 4 for web programming language and MySql for database. Apache web
server is use as the system is a web-base system. This fourth phase was the
last phase, which is used in the SDLC methodology. This phase will transfer the
system into the computer accordingly as the user requirement and design.
5.2
Tools use
Hardware
During the implementation hardware that has been use to develop the
Computer Inventory System are as follows:
<TBA>
Software
Below are all software that need to be provided for the development of the
project:

5.3
<TBA>
Coding phase
Modular coding has been implemented during the project. All module has been
divided into two groups and developed by Khairul Nizam and Mohd Kamal
together.
5.4
Testing phase
Unit testing
After all coding has been completed, testing is right away been done. The
testing in question is not “functional testing” (i.e. is the client getting what they
want) but “unit testing” which is making sure that all of the little “units” of code
that been written functional as they are supposed to.
8
CSC555 (Software Engineering)
Computer Inventory System
Mac-Jun 2012
Integration and module testing
This testing methodology has been used since the development need to
integrate among the client/workstation, web server and database server. Both
incremental approach are being adopted to test all the modules.
6
Conclusion
<TBA>
9