College of Electrical & Mechanical Engineering

Department of CSIT, Software Engineering

Undergraduate Project Proposal

Title: web based software project management system for CNET

Software Technologies PLC

Group Members:
No. Name ID

1. Adem Kedir ETS 0091/07

2. Amanuel Alemayehu ETS 0132.00/07
3. Desta Fisiha ETS 0389/07
4. HAshim Nuri TETS 184/07
5. Michael Wondemu ETS 0777/07

Advisor Name: Eleni Teshome Signature

20 November 2017

0
Contents
1. Problem Statement .................................................................................................................................... 1

2. Project Goal and Objectives ...................................................................................................................... 2

2.1. Goals .................................................................................................................................................. 2

2.2. General Objectives ............................................................................................................................. 2

2.3. Specific Objectives ............................................................................................................................ 2

3. Scope ......................................................................................................................................................... 2

4. Significance............................................................................................................................................... 3

5. Methodology ............................................................................................................................................. 3

5.1. Data collection method ...................................................................................................................... 3

5.2. Process Model .................................................................................................................................... 3

5.3. Architecture- type .............................................................................................................................. 3

5.3. System Analysis and Design Methodology ....................................................................................... 3

5.4. Case Tools.......................................................................................................................................... 4

5.5. Testing................................................................................................................................................ 4

6. Project Schedule........................................................................................................................................ 5

7. References ................................................................................................................................................. 8
1. Problem Statement

The software production industry of Ethiopia is not yet fully matured and the number of
software companies is very limited. Among the few software companies CNET is the pioneer of
Ethiopian software production sector. The company was established around 2002. CNET Software
Technologies PLC was established in 2002 at a registered capital of 425,000.00 ETB. The primer
objective of establishment is to provide total system solutions to any type of business enterprise.
The company mainly specialized on ERP (Enterprise Resource Planning) and POS (Point of Sales)
solution and Web design and deployment. CNET main objective is to provide its clients all local
computer- related needs with respect to system analysis, design, software development,
implementation, support and training on the system. The company currently has 18 permanent
employees, more than 150 customers and more than 4500 users trained on our system since
establishment. And it is still actively involving in the market by producing software for potential
fields with growing needs of ICT. This has helped the company to be among the front leaders of
the market. [1]

CNET mostly engages in several software projects in a certain period of time. Managing
these projects are not an easy task. But the company has still managed to stay strong by manually
managing projects without the help of any additional tool or software. But the current system has
some drawbacks which might affect the project in a great deal. Among the tasks of managing
software projects are organizing teams, assigning each team member to a specific task, following
up the progress and completion of tasks, monitoring the overall progress of the project according
to the predefined schedule, referring previous projects work products, organizing the entire
projects work products and other. Handling all this by using a manual paper work is possible, but
using supporting software like Software Projects Management System (SPMP) is more efficient
and effective way of managing one or more projects. As a result of using the manual paper work
projects might face the risk requiring more resource to reach completion.

The software project management system that we are proposing for CNET is a web based
database driven software that will be implemented on client server architecture. And this software
is expected to facilitate the companies work process significantly. It will help project managers to
keep track of the entire software projects activities and work products. Even though there will still

1
be some paper work, the entire process will be supported by the SPMP which will enhance and
improve the existing systems effectiveness and efficiency notably.

2. Project Goal and Objectives

2.1. Goals
The goal of the Software Project Management System is to help create time and cost-
effective software production process. This will increase the competitiveness of software
companies and increase the probability that customers will get their software in the shortest time
and at the minimum cost possible.

2.2. General Objectives

The main objective of this system is designing a web based software project management
system for CNET Software Technologies PLC.

2.3. Specific Objectives

Design interactive and easy to use User Interface.
Design a relational database to store data.
Develop the features that will show the different models and representation of the software
project.
Develop features that enhance team work.
Implement client-server architecture for multiple user access.
Design and develop project work product management system.

3. Scope

The project will only contain the functionalities to manage and monitor software projects
and their work products. But it will not include team development platform features. And also, the
project will not contain functionalities related to human resource (HR) and related financial
matters. Implementation phase of the software project will not be broken down into tasks for the
reason of simplicity it will only be treated as single solid task of the project. We recommend the
implementation should have its own separate software system, which can be easily integrated with
the Software Project Management System (SPMS).

2
4. Significance

This software project is expected to create a suitable work environment by allowing access
to necessary project data as simple as it should be. And it will also greatly minimize the time
consumed to collect and go through previous records and on the process of managing and
monitoring active projects. It will let the project manager to easily keep track of the Project work
products. And most importantly it will assist the effort of completing a software project on time.
Generally, the Software Project Management System (SPMS) will enhance the overall
productivity of software companies and increase their involvement in the software market.

5. Methodology

5.1. Data collection method

To get a precise data from customers the team has will use Interview to get the basic information
and background information about the existing management system.

5.2. Process Model

In our project, we will use Waterfall process model which is a linear sequential (non-iterative)
design approach for software development, in which progress flows in one direction downwards
(like a waterfall) through the phases of conception, initiation, analysis, design, construction,
testing, deployment and maintenance. [2]

5.3. Architecture- type

We will use Three-tier architecture which is a client- server software architecture pattern in which
the interface (presentation), functional process logic (business rules), computer data storage and
data access are developed and maintained as independent modules, most often on separate
platforms. [2]

5.3. System Analysis and Design Methodology

In this project, the team will use Object Oriented System Development methodology (OOSD).
Which has two phases:

3
Object Oriented Analysis (OOA): during this phase, the team will use to model the functions of
the system (use case modeling), find and identify the business objects, organize the objects and
identify the relationship between them and finally model the behavior of the objects.

Object Oriented Design (OOD): during this phase, the team will use to refine the use case model
to reflect the implementation environment, model object interactions and behaviors that support
the use case scenario, and finally update object model to reflect the implementation environment.

5.4. Case Tools

Software/ language Purpose
MS Visio 2013 Draw Diagrams
CSS3, HTML5, Bootstrap, jQuery Client side scripting
PHP, Java Script Server side scripting
Apaches Server
MySQL Work bench Back end or Database
Atom, Notepad++, Editor
XAMPP Integrate Apache server, MySQL Work bench,
&PHP
MS Office Word 2016 For documenting corresponding deliverables
associated with the project
Laravel v 5.5.5 Frame work
Table: 1 Tools used during software development

Hardware Requirements

Computers
Network Cable
Switch
Flash disk / CD

5.5. Testing
Before directly deploying this system, the team will perform different testing for its functionality
and meeting customers need. First the team tests each unit at each phase. So, if a problem is
encountered it will immediately fixed. Second the team will perform an integration testing to check
whether the system meets all the functional requirements. System will be tested using the following
system testing procedures.

4
Alpha testing: -it takes place at the developers site by the internal teams, before release to external
customers. This testing is performed without the involvement of the development teams. [3] In
this testing method, the system will be tested by giving the correct input.

Beta testing: -is also known as user testing takes place at end users site by end users to validate
the usability, functionality, compatibility, and reliability testing. [3] In this testing method, team
will force the system to be tested for incorrect data input. The System will be tested by the customer
at their actual work place.

If any failures occurred while testing the system in all the above testing methods, the team will
take immediate correction beginning where this fault occurred before jumping to next work so that
it will meet the goal. If all the above testing methods are carried out and figure out to be valid the
system will directly be deployed.

6. Project Schedule

Nov 2017
ID Task Name Start Finish Duration
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

1 System Requirement Specification 2017-11-01 2017-11-22 16d

2 Background Overview 2017-11-01 2017-11-01 1d

3 Functional Requirement 2017-11-02 2017-11-06 3d

4 Non-Functional Requirement 2017-11-07 2017-11-10 4d

5 Feasibility Study 2017-11-13 2017-11-22 8d

Figure: 1 Gantt Chart of System Requirement Specification

5
 Nov 2017 Dec 2017
ID Task Name Start Finish Duration
25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

1 System Analysis and Modeling 2017-11-27 2017-12-22 20d

2 overview 2017-11-27 2017-11-27 1d

3 Scenario Based Modeling 2017-11-28 2017-12-07 8d

4 Behavioral/dynamic modeling 2017-12-08 2017-12-14 5d

5 Class-Based Modeling 2017-12-15 2017-12-22 6d

Figure: 2 Gantt Chart for System Analysis and Modeling

Dec 2017 Jan 2018

ID Task Name Start Finish Duration
25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 System Design 2017-12-25 2018-01-16 17d

2 System Design 2017-12-25 2017-12-29 5d

3 Architecture of the System 2018-01-01 2018-01-05 5d

4 Database Design 2018-01-08 2018-01-11 4d

5 User Interface Design 2018-01-11 2018-01-16 4d

Figure: 3 Gantt Chart for System Design

Feb 2018 Mar 2018 Apr 2018 May 2018

ID Task Name Start Finish Duration
2-11 2-18 2-25 3-4 3-11 3-18 3-25 4-1 4-8 4-15 4-22 4-29 5-6 5-13

1 Implementation 2018-02-05 2018-05-18 75d

Figure: 4 Gantt Chart for Implementation

6
 May 2018 Jun 2018
ID Task Name Start Finish Duration
22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

1 Testing 2018-05-22 2018-06-15 19d

2 Specify testing Materials 2018-05-22 2018-05-23 2d

3 Produce draft Test Plan Document 2018-05-24 2018-05-25 2d

4 Get feed back on Test Plan Document 2018-05-25 2018-05-28 2d

5 Produce final Test Plan Document 2018-05-29 2018-05-30 2d

6 Perform unit , Alfa, Beta testing 2018-05-31 2018-06-05 4d

7 Final Implementation 2018-06-06 2018-06-12 5d

8 Demonstration 2018-06-13 2018-06-13 1d

9 Close Project 2018-06-14 2018-06-15 2d

Figure: 5 Gantt Chart for Testing

Nov 2017 Dec 2017 Jan 2018 Feb 2018 Mar 2018 Apr 2018 May 2018 Jun 2018
ID Task Name Start Finish Duration
11-5 11-12 11-19 11-26 12-3 12-10 12-17 12-24 12-31 1-7 1-14 1-21 1-28 2-4 2-11 2-18 2-25 3-4 3-11 3-18 3-25 4-1 4-8 4-15 4-22 4-29 5-6 5-13 5-20 5-27 6-3 6-10

1 System Requirement Specification 2017-11-01 2017-11-22 16d

2 System Analysis & Modeling 2017-11-27 2017-12-22 20d

3 System Desig n 2017-12-25 2018-01-16 17d

4 Implementation 2018-02-05 2018-05-18 75d

5 Testing 2018-05-22 2019-06-17 280d

Figure: 6 Gantt Chart for all Phases

7
7. References

Websites
1) https://www.cnetsoft.com
2) https://wikipedia.com
3) https://tutoriaspoint.com