PDIE Assignment

Project Design
Implementation
BTEC HND in Computing and Systems Development

Acknowledgement
I would like to express my sincere gratitude to ………. for the support and guidance extended by
him. Since I started this assignment he has been providing all the necessary details and instructions
to me. And also I would thankful to HND coordinator……..for all the help and guidance to get
this assignment success.
This assignment bears the imprint of many people. I sincerely thank full to all my friends and my
class mates and also I would like to thank all the staff for providing all necessary lab facilities and
other facilities to finish this assignment.
Last but not least I wish to thank my beloved parents for their support, strength and for everything.
2
Table of Contents
1) Background and Project justification (LO 1.1)......................................................................................... 5

1.1 Briefly describe the motivation/need for such project (problem/ opportunity/ etc.) ........................... 5
1.2 Define the objectives of the project .................................................................................................... 6
1.3 Outline the scope of the intended information system/network system solution. ............................... 8
2) Undertake a literature review and feasibility study on your areas of interest. Provide initial critical
analysis of the outline specification (LO 1.2) ............................................................................................. 14
3) Carry out a detail requirement analysis (LO 1.3) ................................................................................... 15
3.1 Employ appropriate fact finding techniques to gather requirements ................................................ 15
3.2 Use appropriate techniques to check for possible requirement conflicts, inconsistencies, and
incompleteness and resolve them............................................................................................................ 16
3.3 Create appropriate requirements models (such as Context DFD, Logical DFDs or Use case diagram,
Analysis Class diagram etc., if applicable) to help validate requirements. ............................................. 18
Use case diagram .................................................................................................................................... 23
Analysis Class diagram ........................................................................................................................... 25
................................................................................................................................................................ 25
4) Produce an appropriate project plan (LO 1.4) and submit it for the approval from the supervisors ...... 27
5) Project Planning & Methodology selection ............................................................................................ 33
5.1 Define the project scope, budget and schedule: use appropriate tools & techniques to achieve this
(Project management software, WBS, Gantt chart, critical path analysis etc. as appropriate) (LO 2.1) .... 34
Gantt chart using .................................................................................................................................... 36
5.2 Choose appropriate development methodology, tools and techniques to suit your system development,
and justify your selection decisions ............................................................................................................ 37
Project Management Process .............................................................................................................. 39
Why do projects fail? .......................................................................................................................... 41
Project Success.................................................................................................................................... 43
6) Implementation and Evaluation .............................................................................................................. 44
6.1 For the agreed requirement specification create a design specification that communicates architectural
and detail design, justify your design decisions from that of alternative design solutions/options (LO 2.2)
.................................................................................................................................................................... 44
6.2 Use appropriate modeling techniques to capture and communicate your design (LO 2.2) (LO 2.3) ... 46
6.3 Carry out user interface design in accordance to good design practice (LO 2.2) (LO 2.3) .................. 47
3
6.4 Code and implement/Build your system using appropriate software and hardware, networking options.
(LO 2.2) (LO 2.3)........................................................................................................................................ 53
Database Connection Code ......................................................................................................................... 53
6.5 Produce test plans with appropriate test cases to test all aspects of the system (LO 3.1) ..................... 67
6.6 Carry out complete system testing against the requirement specification; record test results and rectify
any errors and shortcomings in the developed system (LO 3.1) (LO 3.2) .................................................. 71
6.7 Roll out the system and obtain user feedback (LO 2.3) (LO 3.1) ......................................................... 74
7) Critical appraisal and conclusion (LO 3.3) ............................................................................................. 77
7.1 Reflect on your own project work; critically appraise the system (how successful your solution?
Pitfalls, shortcomings etc.) .......................................................................................................................... 77
7.2 Identify possible future extensions of your system ............................................................................... 78
8) Presenting and defending the project work ............................................................................................ 78
8.1 Record your project work in an appropriate format (refer Final Report Format) (LO 4.1) .................. 78
References ................................................................................................................................................... 79
4
1) Background and Project justification (LO 1.1)
1.1 Briefly describe the motivation/need for such project (problem/ opportunity/ etc.)
I am the Project Manager of a Project Management company call create an application named as
“TA Enterprises Co” Vehicle Sales and Purchase organization. I am responsible to select
appropriate among the offers available for the company his owner want to design a database for
insert his day to day sales details.
The clients have entrusted you to managed and develop these project on behalf of their interest.
They will provide all financial backup for the success of the event.
I have to ensure that your master plan is accepted and aligned with their corporate inspirations.
The proposal is most important deliverables ever to know that the success of the project
Assumptions:
Project will take one and half months
Project manager is responsible to be reported in writing to the Steering Committee
Drawbacks of current design
 Complicated Network Design

 No backup servers
 Collision of Packets
 Drop in connection
 Network is slow
 No load Balancing
 Network applications won’t function
 All devices cannot communicate with each other
 Configuration problems
 No security
A new network is to be designed for “TA Enterprises Co” which is efficient and productive, crucial
requirements requested by “TA Enterprises Co” are:
 Highly Secure
5
 Efficient
 Reliable
 Redundant
 Security
 Manageability
1.2 Define the objectives of the project

Objectives
This project is mainly concentrated on designing, building and implementing a network within a
selected region in a real working environment, the project will have a deadline of 45 days within
30 days the designing and installation will take place and in the rest 15 days a test will be done to
check various aspects of the network, the test will include:
 Network penetration
 Server security
 Client security
 Cable testing
 Firewall testing
 Router, switch testing.
The careful study of the conditions concerning the project shows that the project has the potential
to stand up to its expectations. The ideas of merging the new vehicle sales and purchasing process
with the already existing procedure reduces the cost of new machinery and also reduce the time
and effort needed to familiarize employees to new machinery. The only downside is that the prices
of raw materials for the new product are considerably high. The project shows high potential in
earning revenue. There are:
 Proper network infrastructure.

 Availability of network resources to all the users.
 Alternate energy supply.
 Maintaining proper bandwidth.
 Reducing traffic
6
 Improving network performance while using applications.
 Backup links should be introduced.
 WAP should be accessible only to organization employees
 The network should have backup servers to store backups daily.
 Maintenance and upgrading should take place without affecting the processes of the
business.
 System should be maintained within minimum disturbances to the users.
 The Downtime of the network should be low or at 0%.
 Resellers, customers and clients should be able to access to their own data without any
problems.
 Server and client configurations should be done properly.
 The hardware used must be easy to use for the front end user.
 IP phones/ VOIP phones should be implemented to reduce call charges.
 New and existing software’s should be compatible with the new hardware.
 Application software should be compatible with existing hardware.
 24*7 help must be available.
 Implementation of CCTV cameras in the interior as well as exterior environment of the
organization.
 Availability of network diagram for future reference
 Network cabling must be done in a proper manner and all the cables must be covered by
casings.
 Implementation of proper IT security policies.
 Contingency plan, disaster management and recovery plan must be developed.
 Physical security devices must be implemented
 Limited access to server room.
7
1.3 Outline the scope of the intended information system/network system solution.
Business Scope
 Communicate efficiently with employees and clients.
 24*7 communications over the internet.
 Customer Satisfaction through online communication.
 A highly reliable ICT system to increase productivity of the organization.
Project Scope
 Proper network design and topology.
 Less hardware and software issue from each node of the network.
 Availability of backup servers to increase reliability.
 Proper distribution of packets and data (No collisions).
 Reducing the down time of the network.
 Increase in speed of the network.
 Complete functioning of network applications
 Communication within the LAN.
 Availability of backup ISP (internet service provider).
 Opportunity of future upgrades.
 Future proof.
 An ICT infrastructure that would cater all the ICT needs of employees.
 Secure ICT infrastructure.
8
Project Stakeholders
Direct Stakeholders Indirect Stakeholders

Project manager Raw material suppliers
Project Team Clients
Management of Power textile --
Table 1
Topology
Selecting a topology will decide most of the factors of the network like the redundancy and the
manageability of the network, the network will function in a proper way only if the nodes are
properly managed and only if the cabling is done properly so that the signal does not drop, a drop
in the signal may occur if the network is too complicated or even if the wires are extended too
long.
Most of the topologies now a day are hybrid topologies which would often include a wireless
section as well, this would not only provide the internet to all the users but the network will also
be highly flexible.
Implementation of a hybrid network would be most considerable to this organization since the
wireless segment with the combination of wired segments will increase the availability of the
network.
Any type of user of any device will have the ability to use the benefits of the network regardless
to wired or not, on the other hand, the entire network will have a backup links if the wired
connections fail to function the wireless will be able to at least temporarily cater the network needs
of the organization
Drawbacks of the existing system
 The network diagram is not available.

 There are no redundancy links.
 High maintenance cost.
 High electricity expenditure.
9
 Frequent loss of packets.
 Frequent signal drops.
 No backup servers.
 The necessary temperature is not maintained for smooth functioning of servers and other
electronic devices.
 Two-third of the network is in the form of bus topology a single damage to the network
cable will affect the rest of the nodes.
 Single point of failures.
 Only one WAP is available which is not able to cater the requirements of the organization.
 Secondary ISP is not available for backup.
 Frequent failure of existing ISP.
 Cabling is not up to standards.
 Cables have been extended more than the capacity as a result inefficiency is high.
 Few printers are available and this is not able to fulfill the requirements of the organization.
Project Phases
 Phase 1: Requirements gathering
In this step as this is the initial stage all the necessary requirements will be gathered through
various methods below are few of the methods used to gather information at “TA
Enterprises Co Organization”:
 Basic requirements by the management.
 Questionnaires from various employees and various departments.
 Individual interviewing about ICT requirements.
 Analyzing behavior of the employees to the exposure of current ICT environment.
 Evaluation of current network through a check list.
 Complete evaluation of the network.
 Conducting Site visits.
Determining of the upgrade and changes may affect the organization.
 Phase 2: Selection and design
10
In this stage the requirements are properly organized and short listed, prototype designs are
made for the network, the network infrastructure diagrams are made for the management
to understand about how the nodes will be placed.
The information gathered from the “Phase 1” will be considered as resources and the
designs will be made and the products that will be used for the network will also be selected
with contrast to the prices. Final step of this phase is to provide a document to the
management with all the necessary details.
 Phase3:Procurement
This phase is mostly about the products necessary for the project implementation, the
requirements gathered from “Phase1” and the details gained after providing the prototype
in “Phase2”, will be used to purchase the products necessary to fulfill the requirements in
this occasion many of the project managers may prepare a project specification to keep a
proper record of all the products necessary for the project.
 Phase4:Project Implementation
This phase could also be known as “project execution” depending on the environment and
the nature of the project, below is the major stages of this phase:
 Stock & Resources
This is the first stage of this phase and one of the most important, the products
purchased in “Phase3” will be documented and put into an inventory management
system, and in this method the stocks purchased will have proper records in soft copy
as well as hard copy. The inventory will be separately categorized for instance the
servers for the server room will be separately documented all the necessary equipment
for an individual department will be separately categorized this will not only keep
records but will also help the project manager to distribute the job roles to separate
teams (division of labor).
 Casing
11
This is the second stage and the implementation of the project the casing of the project
should start from the “Server room”, locations of how the servers will be placed are
decided and how the casing will be placed.
 Cabling
In this stage the cables will be laid and connected to the necessary peripherals, in power
textile CAT7 and fiber optic cables will be running through the network, the fiber optic
will be used only for the core switches since this is the location in which all the traffic
will be transferred.
 Cable Test
This stage is done after the cables are laid all the cables will be tested using a cable
tester, after all of cables are tested the labeling process will take place, this will start
from the location the ISP and the backup ISP will be connected, all the cables will be
labeled so that in future it will be easy for maintenance as well as for upgrades.
Once these cables are proven to be fully functional the cables of the old/previous
network will be removed and the new cables will be connected, by this method the
upgrade of the network will not affect any activity of “TA Enterprises Co is Vehicle
Sales and Purchase organization”. After all this is done the casing of the cables will
be cover and painted.
 Cabling inspection
After the cables are covered with the casing the top ends of the cables will be rechecked
(RJ45 clips), since during the process of painting and ending the cabling damages may
have occurred, once the inspection is done, the basic implementation of the network is
over.
 Power sources
12
In this stage alternative power resources will be considered, backup power and UPS
will be installed to prevent any loss or damage of data, CSU/DSU will also be placed
during this stage since it is related to power and signals.
 Network Peripherals Switches, Routers and IPS/IDS
Old switches and routers will be removed few of the switches might be used for the
new network according to the performance, the cables will be connected to the switches
and the routers will also be connected in turn making the whole network functional,
IDS/IPS will also be installed in this secession so that all the hardware equipment of
the network is completely allocated in a proper system.
 Firewall & Configurations
The hardware firewall will be inserted into the network and also will be configured,
while few of the members of the team will be configuring the servers
Others will be configuring the routers things like load balancing MAC filtering will be
done in this stage and the client PC will also be configured and IP addresses will be
given to the PCs so once this is initiated the network is functional and the organization
could proceed with their work.
 Servers
Installing the previous data and configuring it into the same environment is done in this
stage so that the users will not feel any obstructs while using the new system.
 PABX
The telephone line will also be replaced, new wires will be used and the system will be
reconnected so that the telephone wiring will not have any impact with the network in
future during maintenance.
 Phase5: Review and Evaluation

This is the phase in which all the new implementations will be checked, the phase consist
of feedback methods and evaluations this stage’s main aim is to create a stable working
environment and also to reduce the obstructions for the users. Below are the stages of this
phase:
 Network Testing
13
The entire network will be tested through “Command and Prompt” and various other
tools in this stage only the functions of the network will be tested so that the clients
have the ability to do their daily jobs and communicate through the new network.
 Phase6: User awareness/Training & Education:

The new system may not be very familiar to all the users, so training should be given to
all the employees and all the employees should be educated through mass seminars.
2) Undertake a literature review and feasibility study on your areas of interest. Provide
initial critical analysis of the outline specification (LO 1.2)
The network built in the infrastructure is not suitable for the current infrastructure, an unsuitable
network for an infrastructure leads to various problems this may have occurred since the
architecture of the network was not properly designed. The network topology used is not suitable
since in inappropriate places WAP are used and in appropriate places it is ignored.
A huge cost has been invested on the it infrastructure however the problem is this network does
not provide much support to the business.
The system is not developed as a complete business system due to this fact high cost is spent on
maintenance as well. Many servers are implemented but serve no purpose the cost and maintenance
of these servers is extremely high. There is no alternate current supply for any of the computers in
the system. Redundancy is not thought about while designing of the network this can be seen by
the method of cabling used in the network. The temperature is not constantly maintained in the
server room and this will reduce the life time of the server.
There is no physical or logical security implemented in the network due to this the system is
vulnerable to attacks.
 No details available about the method of cabling the network.

 No backups are taken or available in the network.
 There are no access control methods in the network.
14
3) Carry out a detail requirement analysis (LO 1.3)
3.1 Employ appropriate fact finding techniques to gather requirements
The TA Enterprises Co” Vehicle Sales and Purchase system the analyst needs to do collect facts
and all relevant information. the facts when expressed in quantitative form are termed as data. The
success of any project is depended upon the accuracy of available data. Accurate information can
be collected with help of certain methods/ techniques. These specific methods for finding
information of the system are termed as fact finding techniques. Interview, Questionnaire, Record
View and Observations are the different fact finding techniques used by the analyst. The analyst
may use more than one technique for investigation.
Interview
This method is used to collect the information from groups or individuals. Analyst selects the
people who are related with the system for the interview. In this method the analyst sits face to
face with the people and records their responses. The interviewer must plan in advance the type of
questions he/ she is going to ask and should be ready to answer any type of question. He should
also choose a suitable place and time which will be comfortable for the respondent.
The information collected is quite accurate and reliable as the interviewer can clear and cross check
the doubts there itself. This method also helps gap the areas of misunderstandings and help to
discuss about the future problems. Structured and unstructured are the two sub categories of
Interview. Structured interview is more formal interview where fixed questions are asked and
specific information is collected whereas unstructured interview is more or less like a casual
conversation where in-depth areas topics are covered and other information apart from the topic
may also be obtained.
Questionnaire
It is the technique used to extract information from number of people. This method can be adopted
and used only by an skillful analyst. The Questionnaire consists of series of questions framed
together in logical manner. The questions are simple, clear and to the point. This method is very
useful for attaining information from people who are concerned with the usage of the system and
15
who are living in different countries. The questionnaire can be mailed or send to people by post.
This is the cheapest source of fact finding.
Record View
The information related to the system is published in the sources like newspapers, magazines,
journals, documents etc. This record review helps the analyst to get valuable information about the
system and the organization.
Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the organization
and observes and understand the flow of documents, working of the existing system, the users of
the system etc. For this method to be adopted it takes an analyst to perform this job as he knows
which points should be noticed and highlighted. In analyst may observe the unwanted things as
well and simply cause delay in the development of the new system.
3.2 Use appropriate techniques to check for possible requirement conflicts, inconsistencies,
and incompleteness and resolve them
Features of the success or failure of a project
Success criteria factors
 Formulating and planning of the project – A feasibility study could be conducted in

order to identify the time period, costs and resources and staff needed in order to pledge
the project. All these triple constraints have to be identified before starting the project.
 Time management – Effectively making use of the time allocated before the deadline and
completing the project with the expected level of quality. Allocating a time for each task
would help in the completion of the project before the deadline.
 Effective team work – Having an efficient and motivated team would help in increasing
the productivity of the organization and help achieve the opportunities and requirements
of the customer. Working together as a team would help to meet all the expectations of
the user and help in performing all the tasks as stated in the project, thereby making the
project a success.
16
 Support from the executive management – The strategic level management is kept
informed about the project standards and processes and the feedback is sent to the project
managers, regarding any changes to be made, thereby enabling an effective
communication approach.
 All the requirements stated clearly to the employees – employees know what is
required by them to perform during the project beginning till the closure of the project.
Having a sense of understanding of the project requirements would help in successfully
completing the project.
Failure criteria factors
These factors are the opposite of the success criteria factors. A clarification of these factors
mentioned below is described on the success criteria factors.
1. No proper planning and preparation

2. Poor time management of tasks
3. Poor knowledge on the requirements of the project
4. Majority of unrealistic expectations
5. Lack of executive support
6. Incomplete requirements
7. Poor user involvement
8. Using lack of resources
9. Changing requirements & specifications
10. Poor Planning sessions
11. Poor management in IT
12. Technical capabilities
13. Not necessary to complete project Any Longer
14. Poor team work management
 Initial Technical Evaluation (Phase 1)
This is the first phase of evaluating an individual, the procedure is mostly followed by project
managers during the “recruitment” stage, and each individual will be evaluated with
“experience and technical knowledge”, along with the expected wage/salary.
17
 Allocation Into Technical Environment (Phase 2)
This is the monitoring performed by the higher management regarding the new employees
that were primarily evaluated in phase1,the employees will be put into the practical
environment where the skills and experience will be tested an monitored this is usually done
on the job.
 Final Technical Evaluation (Phase 3)

This is the final stage, in which the technical evaluation of human resources would be done,
according to the skills, experience and knowledge, with contrast to the cost/salary/wages the
evaluation will be performed and selection as well as allocation would be done.
3.3 Create appropriate requirements models (such as Context DFD, Logical DFDs or Use
case diagram, Analysis Class diagram etc., if applicable) to help validate requirements.
DATA FLOW
1) A Data Flow has only one direction of flow between symbols. It may flow in both directions
between a process and a data store to show a read before an update. The later is usually
indicated however by two separate arrows since these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or more different
processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must be at least one
other process that handles the data flow produce some other data flow returns the original data
into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can appear on a single
arrow as long as all of the flows on the same arrow move together as one package.
18
Context DFD
Admin Cool Cab User

Services
Cool Cab Admin

User Services
Logical DFDs
19
Level 1 Diagram Admin
HR
Manager
Maintanance
Manager
Id & Password Valid Id &

Admin Register Movement
InValid Id & Password
Manager
Password
Finance
Manager
Quality
Assurance
DB
Manager
Level 2 Diagram Maintenance manager
20
Driver
Details
Vendor
Details
Maintenance Id & Password Valid Id&

Manager Invalid Id& Password Maintain Vehicle
Password Details
Spare part
Details
DB
Spare part
Billing
Level 2 Diagram Movement manager
21
Route
Trip Details
Sheet
Driver
Shift
Details
Movement Id & Password Valid Id&

Maintain Route
Manager Invalid Id& Password
Password
Search
Shift
Search
DB
Vehicle
Vehicle
Allocation
Search
22
Use case diagram
Admin
Create
Accounts
Maintain
Account
Details
Admin
Login
HR Manager
Employee
Information
Shift Timing
Information
Shift Shedule
Information
HR Manager
Batch Details
View Hr manager
profile
23
Maintenance Manager
Drier
Details
Vendor
Details
Vehicle
Details
Maintenance
Manager
spare part
Details
spare part
billing
Finance Manager
Vehicle
Billing
Vendor
Billing
Finance
Manager
View
Profile
24
Analysis Class diagram
25
3.4 Prepare the requirement specification of the system clearly documenting all the
functional and non-functional requirements and state any assumptions or constraints there
therein
In the developed system, Details are Stored Manually in papers, to share the details between
employees was a financial drawback. Pupations in the details is a tedious task.
But a new system was proposed to overcome the above drawbacks.
Functionalities and advantages of proposed system are:
 Data is centralized which has overcome the Sharing problem in previous system.
 As data is maintained electronically, it’s easy for a person to update the details, which has
overcome the tedious updating in previous system
 Maintenance is easy and performance is good
 Mainly the system has automated the Transportation Process
Functionalities
 Association Employee and shift schedule

 Association between Customer Registration and Sales Details
 Association between batch and Schedule times
 Association between shift schedule and Supplier details
 Adding Customers and providing ids
Queries
 What is the Employee id of an Employee?

 What is the total number of Employees?
 What is the Batch id of an empid?
 What is the total number of employees in a batch.?
26
4) Produce an appropriate project plan (LO 1.4) and submit it for the approval from the
supervisors
Phase Task Resources
Requirement Gathering (Phase 01) Individual Interviews  Employees.
Requirement Gathering (Phase 01) Basic Requirements Provided by  Management.
Management.  Documents.
Requirement Gathering (Phase 01)  Employees.
General Questionnaires  System Users.
 Management.
Requirement Gathering (Phase 01) Personal Evaluation of Current  System.
System  Project Manager
Requirement Gathering (Phase 01) Evaluation of current network  Checklist
through  Network
a check list.
Requirement Gathering (Phase 01) Analyzing behavior of the  Employees
employees to the exposure of  System Users.
current ICT environment.  ICT Devices
Requirement Gathering (Phase 01) Analysis through Project  Project Team.
Technical Team  ICT Environment.
Requirement Gathering (Phase 01) Site Visits  ICT Infrastructure.

Selection & Design (Phase 2) Virtual Creation of Network  Computer.
Architecture  Ms visio
Selection & Design (Phase 2) Creation of Multiple Network  Ms visio
Designs/Topologies  Printing Paper
Selection & Design (Phase 2)  Paper.
Documentation of Each Design  Computer.
 Ms Word.
 Documenter
27
Selection & Design (Phase 2) Virtual 3D Modeling of  Computer
Infrastructure
Selection & Design (Phase 2) Physical Modeling of  Modeling Material
Infrastructure & Topology
Selection & Design (Phase 2) Presentation of Design and  Presenter.
documents to Management  Design.
 Documents.
 Presentation.
Selection & Design (Phase 2)  Design.
Documentation of final Design  Ms Word.
 Documenter
 Computer
Selection & Design (Phase 2) Approval of final design &  Management.
Architecture  Documents.
 Design.
Procurement (Phase 3) Market Research Of Products  Market.
 Researcher.
Procurement (Phase 3)  Ms word.
Document Of Product  Documenter.
Specifications  Product Details.
Procurement (Phase 3) Obtaining Quotations  Seller.
 Researcher.
Procurement (Phase 3)  Sellers.
Products & Price Comparison  Brands.
 Prices.
Procurement (Phase 3) Warranty checking  Brands.
 Sellers.
 Warranty Card.
Procurement (Phase 3) Future Maintenance Cost of  Knowledge about Maintenance.
Products.
28
 Methods of Maintenance.
 Market Prices of Maintenance.
 Documentation.
Procurement (Phase 3) Check up for substitutes.  Researcher.
 Market.
 Products.
Procurement (Phase 3) Presentation of Cost & Product  Presenter.
types To Management.  Presentation.
 Price Documents.
 Product Documents.
Procurement (Phase 3) Purchase of Products.  Finance.
Procurement (Phase 3) Check for any faults with  Products.
Purchased Vehicle Parts.  Bills.
 Project Team.
Implementation (Phase 4)  Inventory Management Software.
Creation of Sales and Inventory.  Computer.
 Products.
 Data Entry Operators.
Implementation (Phase 4)  Plastic Cases.
 Nails.
Documenting.  Drills.
 Hammer.
 Man Power/Project Team
Implementation (Phase 4)  RJ-45.
 Fiber optic.
 Cable Cutter.
System Design.  Blade.
 RJ-45 Connector.
 Fiber Optic connector.
29
 Project Team.
Implementation (Phase 4) Cable Testing.  Cable Tester.
 Project Team.
Implementation (Phase 4) Cable Inspection.  Magnifying Glass.
 Project Team.
Implementation (Phase 4)  CSU/DSU.
Backup Energy.  UPS.
 Project Team.
Implementation (Phase 4)  IDS/IPS.
Network Peripherals.  Switches.
 Routers.
 WAP.
 Project Team.
 Network Diagram.
Implementation (Phase 4)  Biometric Scanners.
Physical Security.  Lock & Key.
 Project Team.
 Network Diagram.
Implementation (Phase 4)  Network Diagram.
 Servers.
Network Nodes.  Desktops.
 Printers.
 Scanners.
 Project Team.
Implementation (Phase 4) PABX.  Cables.
 Project Team.
Implementation (Phase 4)  Firewall.
 Servers.
 Desktops.
30
Firewall & Configuration.  Routers.
 WAP.
 ISPs.
 Operating Systems.
 Project Team.
 Ethical Hacker.
 Backtrack.
Review & Evaluation (Phase 5) Penetration/Security Test.  Security Tools.
 Laptop.
 Ethernet.
 Server.
 Desktop.
Review & Evaluation (Phase 5)  Routers.
Network Testing.  Switches.
 WAP.
 Firewall.
 ISP.
 Project Team.
Review & Evaluation (Phase 5) Documentation of Pentest,  Computer.
Security test and Network Test.  MS word.
 Documenter.
Review & Evaluation (Phase 5) Collecting User Feedback.  System Users.
 Management.
Review & Evaluation (Phase 5) Documentation of Feedback.  Documenter.
 Computer.
 MS word.
Review & Evaluation (Phase 5) Changes to System According  System.
to Feedback.  Project Team.
 Documents.
31
User awareness/Training & Seminars  Project Team.
Education (Phase 6)  Documents.
 System Users.
User awareness/Training &  System.
Education (Phase 6) On the Job Training  System Users.
 Project Team.
32
5) Project Planning & Methodology selection
33
5.1 Define the project scope, budget and schedule: use appropriate tools & techniques to
achieve this (Project management software, WBS, Gantt chart, critical path analysis etc. as
appropriate) (LO 2.1)
There are resources and allocating resources efficiently will lead any project to success, analyzing
the scare resources of a project will help the team not only to reduce cost but also to reduce
opportunities of exhausting the resource.
Usually while managing a project the resources will be allocated with contrast to the phases of the
project and according to the “Work Break down Structure”.
The project manager will usually prepare an inventory of all the resources available and record the
scarce resources as well, in this way the resources can be used efficiently and a proper record will
be available. While deciding which resources are quite necessary for the project a checklist as well
as a self-questionnaire for the project manager would be advisable. The specifications of the client
as well as the sustainability of the resource should be checked before selecting any resource for
execution of the project.
Questionnaire:
 What instance would the resource be mostly used?

 Is there in substitute in the market for this resource?
 What is the lowest price of the substitute in the market?
 What are the drawbacks of the resource I selected?
 How would the selected resource help to deduct the cost of the project?
 Is the resource able to stand natural disasters?
 By selecting the resource would the total cost ownership reduce?
 Will the maintenance cost be high of the resource?
Above is a sample questionnaire that could be used for the project manager, the resources used
should be separately given to the team to do a market research about the product, for instance in
the phase of cabling the team will have to separately do a research with regards to the cables
available in the market.
34
For instance in cabling a wide range of products are available from fiber optic to CAT-7 cables
are available the prices should be compared with the specifications, if we implement Fiber optic
maintenance would be costly while CAT-7 would be easy to maintain, in the initial cost fiber optic
and CAT-7 are almost the same price as well.
When it comes to selecting the resource proper evaluation should be done since a single mistake
would lead to huge changes in cost as well as this will affect the future of the organization. After
proper selection of resource only then resource should be allocated.
When it comes to the factor of resources in any project is crucial the resources are generally
handled by the “Resource Manager” and sometimes the “Project Manager” also is involved in
management of resources, there are mainly 2 types of resources in any project:
 Scarce Resources.
 Available Resources.
Prepare a product breakdown structure
These are resources that are not much available, scarce resources may differ from project to project
however in each project there is a higher probability that some of the resources are scarce, scarce
resources maybe financially accessible but not physical the project sponsors could have the
purchasing power to invest in a resource but due to the lack of availability the resource becomes
“Scarce”.
Available Resources
These are resources which are freely available in existence and access to the project due to this
reason these resources are not as demanded as scarce resources however these resources may also
be scarce if and when it is not allocated and efficiently used
Below is a table which plays the roles of keeping in track of resources necessary for each task, by
this way the project team as well as the project manager will know which resources should be
utilized in each phase.
35
Gantt chart using
36
5.2 Choose appropriate development methodology, tools and techniques to suit your system
development, and justify your selection decisions
Human Resource and Management
Human resource is the basic resource necessary for the project to function, without the
coordination of humans other resources will not be able to function it is not only necessary to
check smooth functioning of the “Project Team” members but also the Project Manager must be
peculiar about the employees of “Power Textile”, the employees may not be actively or partially
involved in the project but if and when there is any obstacle for the employees of power textile
due to implementation of the project the project manager must coordinate in way the obstacle is
rectified.
Factors to be considered about human resources by the “Project Manager”:
 Efficient allocation of Human Resource.

 Working conditions.
 Worker Motivation.
Allocation of human resources is done in every project the question which arises is weather the
allocation of human resources is “efficient”?, the term efficiency is one of the most necessary
criteria in any project the entire success and completion depends upon the efficiency of the
resources.
In the project of “power textile” there is a lot of skilled human work force necessary, the factor of
just having the skilled work force is necessarily enough effective efficiency and efficient allocation
is necessary, since this project is more related to the technical aspect it is necessary to consider the
technical level of skill in the available work force.
Generally technical skills are obtained by the employees that have “high experience”, it is a matter
of the employees which have more “on the job” trainings are likely to be experts in the technical
field however for the selection and allocation of employees for the project at “power textile”, the
below method was implemented.
37
Allocation Into
Initial Technical Final Technical
Technical
Evaluation Evaluation (Phase
Environment
(Phase 1) 3)
(Phase 2)
Figure 1
Net Present Value (NPV), benefits analysis and viability of the project to determine the
success or failure of the selected project
Net present value method (also known as discounted cash flow method) is a popular capital
budgeting technique that takes into account the time value of money.
It uses net present value of the investment project as the base to accept or reject a proposed
investment in projects like purchase of new equipment, purchase of inventory, expansion or
addition of existing plant assets and the installation of new plants etc.
Figure 3-2 Net Present Value Method
• Takes into account the fact that money values change with time
38
• How much would you need to invest today to earn x amount in x years’ time?
• Value of money is affected by interest rates
• NPV helps to take these factors into consideration
• Shows you what your investment would have earned in an alternative investment regime
For example, an investment of $500,000 today is expected to return $100,000 of cash each year
for 10 years. The $500,000 being spent today is already a present value, so no discounting is
necessary for this amount. However, the future cash receipts of $100,000 for 10 years need to be
discounted to their present value. Let's assume that the receipts are discounted by 14% (the
company's required return). This will mean that the present value of the future receipts will be
approximately $522,000. The $522,000 of present value coming in is compared to the $500,000
of present value going out. The result is a net present value of $22,000 coming in.
Project Management Process

Project management is an integrative endeavor; decisions and actions taken in one knowledge area
at a certain time usually affect other knowledge areas. Managing these interactions often requires
making trade-offs among the project s scope, time, and cost the triple constraint of project
management.
A project manager may also need to make trade-offs between other knowledge areas, such as
between risk and human resources. Consequently, you can view project management as a number
of related processes.
A process is a series of actions directed toward a particular result. Project management process
groups’ progress from initiating activities to planning activities, executing activities, monitoring
and controlling activities, and closing activities. Initiating processes include defining and
authorizing a project or project phase. Initiating processes take place during each phase of a
project. Therefore, you cannot equate process groups with project phases. Recall that there can be
different project phases, but all projects will include all five process groups. For example, project
managers and teams should reexamine the business need for the project during every phase of the
project life cycle to determine if the project is worth continuing. Initiating processes are also
required to end a project. Someone must initiate activities to ensure that the project team completes
39
all the work, documents lessons learned, assigns project resources, and that the customer accepts
the work.
Planning processes include devising and maintaining a workable scheme to ensure that the project
addresses the organization s needs. There are several plans for projects, such as the scope
management plan, schedule management plan, cost management plan, procurement management
plan, and so on, defining each knowledge area as it relates to the project at that point in time. For
example, a project team must develop a plan to define the work that needs to be done for the
project, to schedule activities related to that work, to estimate costs for performing the work, to
decide what resources to procure to accomplish the work, and so on.
To account for changing conditions on the project and in the organization, project teams often
revise plans during each phase of the project life cycle. The project management plan coordinates
and encompasses information from all other plans. Executing processes include coordinating
people and other resources to carry out the various plans and produce the products, services, or
results of the project or phase. Examples of executing processes include acquiring and developing
the project team, performing quality assurance, distributing information, managing stakeholder
expectations, and conducting procurements. Monitoring and controlling processes include
regularly measuring and monitoring progress to ensure that the project team meets the project
objectives. The project manager and staff monitor and measure progress against the plans and take
corrective action when necessary. A common monitoring and controlling process is reporting
performance, where project stakeholders can identify any necessary changes that may be required
to keep the project on track.
Closing processes include formalizing acceptance of the project or project phase and ending it
efficiently. Administrative activities are often involved in this process group, such as archiving
project files, closing out contracts, documenting lessons learned, and receiving formal acceptance
of the delivered work as part of the phase or project.
40
Figure 3-3 Percentage of time spent on each process
Why do projects fail?

We can probably all think of projects that have “failed”, perhaps processes got worse rather than
better, maybe they were cancelled because of cost overruns, or perhaps systems were launched
with fundamental errors.
How do you know when and why a project has failed? In many cases, the reason for failure is
obvious. However, the definition of failure isn't always clear: one project with a significant delay
might be described as a failure; yet another, with a similar delay, might be seen as a striking
success.
1. Lack of User Involvement - Lack of user involvement has proved fatal for many projects.
Without user involvement nobody in the business senses committed to a system, and can even
be hostile to it.
If a project is to be a success senior management and users need to be involved from the start,
and continuously throughout the development. This requires time and effort, and when the
people in a business are already stretched, finding time for a new project is not high on their
priorities.
2. Long or Unrealistic Time Scales - Long timescales for a project have led to systems being
delivered for products and services no longer in use by an organization.
The key recommendation is that project timescales should be short, which means that larger
systems should be split into separate projects. There are always problems with this approach, but
the benefits of doing so are considerable.
41
3. Poor or No Requirements - Many projects have high level, vague, and generally unhelpful
requirements.
This has led to cases where the developers, having no input from the users, build what they believe
is needed, without having any real knowledge of the business. Inevitably when the system is
delivered business users say it does not do what they need it to
4. Scope Creep - Scope is the overall view of what a system will deliver. Scope creep is the
insidious growth in the scale of a system during the life of a project.
As an example for a system which will hold customer records, it is then decided it will also deal
with customer bills, then these bills will be provided on the Internet, and so on and so forth. All
the functionality will have to be delivered at one time, therefore affecting time scales, and all will
have to have detailed requirements. This is a management issue closely related to change control.
5. Poor Testing - The developers will do a great deal of testing during development, but
eventually the users must run acceptance tests to see if the system meets the business
requirements. However acceptance testing often fails to catch many faults before a system goes
live because:
 Poor requirements which cannot be tested

 Poorly, or non-planned tests meaning that the system is not methodically checked
 Inadequately trained users who do not know what the purpose of testing is
 Inadequate time to perform tests as the project is late
Users, in order to build their confidence with a system, and to utilize their experience of the
business, should do the acceptance testing. To do so they need good testable requirements, well
designed and planned tests, be adequately trained, and have sufficient time to achieve the testing
objectives.
6. No Change Control System - Despite everything businesses change, and change is happening
at a faster rate than ever before. So it is not realistic to expect no change in requirements while
a system is being built.
However uncontrolled changes play havoc with a system under development and have caused
many project failures.
42
7. Conclusion - These six factors are not the only ones that affect the success or failure of a
project, but in many studies and reports they appear near, or at the top of the list. They are all
interlinked, but as can be seen they are not technical issues, but management and training ones.
Project Success
How do you define the success or failure of a project? There are several ways to define project
success. The list that follows outlines a few common criteria for measuring the success of a project:
1. The project met scope, time, and cost goals. If all 100 computers were upgraded and met other
scope requirements, the work was completed in three months or less, and the cost was
Rs.100,000/- or less, you could consider it a successful project based on this criterion.
2. The Standish Group studies used this definition of success. Several people question this
simple definition of project success and the methods used for collecting the data.
3. The project satisfied the customer/sponsor. Even if the project met initial scope, time, and
cost goals, the users of the computers or their managers might not be satisfied. Perhaps the
project manager or team members never returned calls or were rude.
Perhaps users had their daily work disrupted during the upgrades or had to work extra hours due
to the upgrades. If the customers were not happy with important aspects of the project, it would
be deemed a failure.
Conversely, a project might not meet initial scope, time, and cost goals, but the customer could
still be very satisfied. Perhaps the project team took longer and spent more money than planned,
but they were very polite and helped the users and managers solve several work-related problems.
Many organizations implement a customer satisfaction rating system for projects to measure
project success instead of only tracking scope, time, and cost performance.
4. The results of the project met its main objective, such as making or saving a certain amount
of money, providing a good return on investment, or simply making the sponsors happy.
43
5. Even if the project cost more than estimated, took longer to complete, and the project team
was hard to work with, if the users were happy with the upgraded computers it would be a
successful project, based on this criterion.
As another example, suppose the sponsor really approved the upgrade project to provide a good
return on investment by speeding up work and therefore generating more profits. If those goals
were met, the sponsor would deem the project a success, regardless of other factors involved.
6) Implementation and Evaluation
6.1 For the agreed requirement specification create a design specification that communicates
architectural and detail design, justify your design decisions from that of alternative design
solutions/options (LO 2.2)
Project manager
44
An individual or a group, who is professionally applicable and responsible for planning execution
and success of projects, the entire project basically, is decided by the project manager, and the
success of the project depends on the upon the experience and maintenance done by the project
manager, depending on the organization the project manager may differ, project managers could
be temporary or a permanent position.
A project manager will have to first discuss and collect information from the client; a project
manager could be a client side representative or could be a project manager from a project
management.
Monitoring and ensuring the project team will complete the projects on time is one of the many
job roles the project manager would do. Project managers are responsible for the motivation as
well as ensuring proper working conditions for the project team and the subordinates.
Developing a workable culture within the project and reducing errors will also be in the hands of
the project manager, project managers are usually a position attained after a minimum of 5 years
in the industry of handling large scale projects. The project manager should also develop the
project plan ad allocate jobs to the project team.
The Project Manager Should have knowledge about various sections in the industry including
administration, human resource, customer care etc. since each of these functions will be useful
administration will be necessary while documentation of the project while human resource will be
necessary while allocating and managing the project team, knowledge about analysis and about
products in the market will also have to be obtained.
In some projects there are several project managers since the project is too intensive for one
individual to handle, usually when there are several project managers there will be a “Senior
Project manager “ who will be in charge of all the other project managers depending upon the
project and the experience the role of the project manager will be different.
The title “project manager” is given only to an individual who is able to take complete
responsibility of a certain project. There are several types of project managers:
 Senior Project Manager/Project Manager

 Junior Project Manager
45
 Assistant project manager
6.2 Use appropriate modeling techniques to capture and communicate your design (LO 2.2)
(LO 2.3)
Depending upon the organization and the project the title will differ, however the “Senior Project
Manager” also known as the “Project Manager” is seen as the head of the entire project in large
projects as described above the senior project manager will monitor the functions of the project
managers, the subordinates.
While the junior project managers will have to view and monitor the project team and ensure all
the tasks are completed successfully on time, the “Assistant project manager” is a title given to
an individual that would help the “Senior project manager” or “Junior Project Manager” with
the functions the assistant project manager is usually a secretary who would ensure the project
managers would not under-estimate or overestimated any and each task of the project.
Project Team Leader
The project team leader is the individual the team should report to about the progress, the team
leader is usually an individual who is responsible and accountable for the team working with the
him/her, the team leaders also. It’s usually reported about the daily activities of the team, the team
leader will be specialized usually in one sector and will be have the knowledge about management
since when the raw material is provided to the team if proper management is not done a lot of
finance would be spent on the raw materials and as a result it would be over costing of the project.
Review and approve all project deliverables (Initiation Plan, Detailed Plan, Testing etc.)
 Provide overall project oversight and work with business offices and Technical Project
manager to keep project on track.
 Ensures business and functional decisions are made to ensure technical development progress
and completion
 Work with Change Manager to develop Campus Readiness plan and related deliverables
46
6.3 Carry out user interface design in accordance to good design practice (LO 2.2) (LO 2.3)
Main UI
47
Sales UI
48
Customer Registration UI
49
Items Details UI
Return Details UI
50
Supplier UI
51
User Registration UI
52
6.4 Code and implement/Build your system using appropriate software and hardware,
networking options. (LO 2.2) (LO 2.3)
Database Connection Code

using System.Collections.Generic;
using System.Linq;
using System.Text;
namespace DMS
class DBconn
public string DBConn = @"Data Source=Nadeeka\SQLEXPRESS;Initial Catalog=DMS; Integrated Security=True";
Customer Code
namespace DMS
partial class frmCustomer
/// <summary>
/// Required designer variable.
/// </summary>
private System.ComponentModel.IContainer components = null;
/// <summary>
/// Clean up any resources being used.
/// </summary>
53
/// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
protected override void Dispose(bool disposing)
if (disposing && (components != null))
components.Dispose();
base.Dispose(disposing);
#region Windows Form Designer generated code
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
this.dateTimePicker1 = new System.Windows.Forms.DateTimePicker();
this.txtCustomerID = new System.Windows.Forms.TextBox();
this.txtContactNo1 = new System.Windows.Forms.TextBox();
this.Label4 = new System.Windows.Forms.Label();
this.txtContactNo = new System.Windows.Forms.TextBox();
this.txtCustomerName = new System.Windows.Forms.TextBox();
this.txtNotes = new System.Windows.Forms.TextBox();
this.txtEmail = new System.Windows.Forms.TextBox();
54
this.label1 = new System.Windows.Forms.Label();
this.txtAddress = new System.Windows.Forms.TextBox();
this.groupBox1.SuspendLayout();
this.SuspendLayout();
//
// dateTimePicker1
//
this.dateTimePicker1.Format = System.Windows.Forms.DateTimePickerFormat.Short;
this.dateTimePicker1.Location = new System.Drawing.Point(148, 446);
this.dateTimePicker1.Name = "dateTimePicker1";
this.dateTimePicker1.Size = new System.Drawing.Size(200, 25);
this.dateTimePicker1.TabIndex = 104;
//
// txtCustomerID
//
this.txtCustomerID.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

System.Drawing.GraphicsUnit.Point, ((byte)(0)));
this.txtCustomerID.Location = new System.Drawing.Point(148, 29);
this.txtCustomerID.Name = "txtCustomerID";
this.txtCustomerID.ReadOnly = true;
this.txtCustomerID.Size = new System.Drawing.Size(118, 25);
this.txtCustomerID.TabIndex = 85;
//
// txtContactNo1
55
//
this.txtContactNo1.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.txtContactNo1.Location = new System.Drawing.Point(147, 254);
this.txtContactNo1.Name = "txtContactNo1";
this.txtContactNo1.Size = new System.Drawing.Size(119, 25);
this.txtContactNo1.TabIndex = 4;
//
// Label4
//
this.Label4.AutoSize = true;
this.Label4.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.Label4.Location = new System.Drawing.Point(24, 29);
this.Label4.Name = "Label4";
this.Label4.Size = new System.Drawing.Size(80, 17);
this.Label4.TabIndex = 88;
this.Label4.Text = "Customer ID";
//
// txtContactNo
//
this.txtContactNo.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.txtContactNo.Location = new System.Drawing.Point(147, 213);
this.txtContactNo.Name = "txtContactNo";
this.txtContactNo.Size = new System.Drawing.Size(119, 25);
this.txtContactNo.TabIndex = 3;
//
56
// txtCustomerName
//
this.txtCustomerName.Font = new System.Drawing.Font("Segoe UI", 9.75F,

System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, ((byte)(0)));
this.txtCustomerName.Location = new System.Drawing.Point(147, 70);
this.txtCustomerName.Name = "txtCustomerName";
this.txtCustomerName.Size = new System.Drawing.Size(273, 25);
this.txtCustomerName.TabIndex = 0;
//
// txtNotes
//
this.txtNotes.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.txtNotes.Location = new System.Drawing.Point(147, 336);
this.txtNotes.Multiline = true;
this.txtNotes.Name = "txtNotes";
this.txtNotes.ScrollBars = System.Windows.Forms.ScrollBars.Both;
this.txtNotes.Size = new System.Drawing.Size(251, 94);
this.txtNotes.TabIndex = 6;
//
// Label2
//

57
this.Label2.Text = "Name";
//
// txtEmail
//
this.txtEmail.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.txtEmail.Location = new System.Drawing.Point(147, 295);
this.txtEmail.Name = "txtEmail";
this.txtEmail.Size = new System.Drawing.Size(226, 25);
this.txtEmail.TabIndex = 5;
//
// Label5
//

this.Label5.Text = "Address";
//
// label1
//
this.label1.AutoSize = true;
this.label1.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

58
this.label1.Location = new System.Drawing.Point(24, 452);
this.label1.Name = "label1";
this.label1.Size = new System.Drawing.Size(62, 17);
this.label1.TabIndex = 95;
this.label1.Text = "Join Date";
//
// Label23
//

this.Label23.Text = "Notes";
//
// Label21
//

this.Label21.Text = "Tel-No";
//
59
// txtAddress
//
this.txtAddress.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.txtAddress.Location = new System.Drawing.Point(147, 111);
this.txtAddress.Multiline = true;
this.txtAddress.Name = "txtAddress";
this.txtAddress.Size = new System.Drawing.Size(273, 45);
this.txtAddress.TabIndex = 1;
//
// Label20
//

this.Label20.Text = "Email";
//
// Label19
//

60
this.Label19.Text = "Mobile No";
//
// panel1
//
this.panel1.BackColor = System.Drawing.Color.FromArgb(((int)(((byte)(37)))), ((int)(((byte)(46)))),

((int)(((byte)(59)))));
this.panel1.BorderStyle = System.Windows.Forms.BorderStyle.FixedSingle;
this.panel1.Controls.Add(this.btnGetData);
this.panel1.Controls.Add(this.btnNew);
this.panel1.Controls.Add(this.btnSave);
this.panel1.Controls.Add(this.btnUpdate);
this.panel1.Controls.Add(this.btnDelete);
this.panel1.Dock = System.Windows.Forms.DockStyle.Left;
this.panel1.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.panel1.Location = new System.Drawing.Point(0, 0);
this.panel1.Name = "panel1";
this.panel1.Size = new System.Drawing.Size(148, 510);
this.panel1.TabIndex = 104;
//
// btnGetData
//
this.btnGetData.Cursor = System.Windows.Forms.Cursors.Hand;
this.btnGetData.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnGetData.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

61
this.btnGetData.ForeColor = System.Drawing.Color.White;
this.btnGetData.Image = global::DMS.Properties.Resources.Database_Table_icon;
this.btnGetData.ImageAlign = System.Drawing.ContentAlignment.MiddleLeft;
this.btnGetData.Location = new System.Drawing.Point(11, 271);
this.btnGetData.Name = "btnGetData";
this.btnGetData.Size = new System.Drawing.Size(119, 59);
this.btnGetData.TabIndex = 19;
this.btnGetData.Text = "&Get Data";
this.btnGetData.TextAlign = System.Drawing.ContentAlignment.MiddleRight;
this.btnGetData.UseVisualStyleBackColor = true;
this.btnGetData.Click += new System.EventHandler(this.btnGetData_Click);
//
// btnNew
//
this.btnNew.Cursor = System.Windows.Forms.Cursors.Hand;
this.btnNew.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnNew.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.btnNew.ForeColor = System.Drawing.Color.White;
this.btnNew.Image = global::DMS.Properties.Resources.Actions_edit_paste_icon32;
this.btnNew.ImageAlign = System.Drawing.ContentAlignment.MiddleLeft;
this.btnNew.Location = new System.Drawing.Point(11, 11);
this.btnNew.Name = "btnNew";
this.btnNew.Size = new System.Drawing.Size(119, 59);
this.btnNew.TabIndex = 10;
this.btnNew.Text = "&New";
this.btnNew.TextAlign = System.Drawing.ContentAlignment.MiddleRight;
62
this.btnNew.UseVisualStyleBackColor = true;
this.btnNew.Click += new System.EventHandler(this.btnNew_Click);
//
// btnSave
//
this.btnSave.Cursor = System.Windows.Forms.Cursors.Hand;
this.btnSave.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnSave.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.btnSave.ForeColor = System.Drawing.Color.White;
this.btnSave.Image = global::DMS.Properties.Resources.Actions_document_save_icon48;
this.btnSave.ImageAlign = System.Drawing.ContentAlignment.MiddleLeft;
this.btnSave.Location = new System.Drawing.Point(11, 76);
this.btnSave.Name = "btnSave";
this.btnSave.Size = new System.Drawing.Size(119, 59);
this.btnSave.TabIndex = 16;
this.btnSave.Text = "&Save";
this.btnSave.TextAlign = System.Drawing.ContentAlignment.MiddleRight;
this.btnSave.UseVisualStyleBackColor = true;
this.btnSave.Click += new System.EventHandler(this.btnSave_Click);
//
// btnUpdate
//
this.btnUpdate.Cursor = System.Windows.Forms.Cursors.Hand;
this.btnUpdate.Enabled = false;
this.btnUpdate.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnUpdate.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

63
this.btnUpdate.ForeColor = System.Drawing.Color.White;
this.btnUpdate.Image = global::DMS.Properties.Resources.Files_Edit_file_icon;
this.btnUpdate.ImageAlign = System.Drawing.ContentAlignment.MiddleLeft;
this.btnUpdate.Location = new System.Drawing.Point(11, 141);
this.btnUpdate.Name = "btnUpdate";
this.btnUpdate.Size = new System.Drawing.Size(119, 59);
this.btnUpdate.TabIndex = 17;
this.btnUpdate.Text = "&Update";
this.btnUpdate.TextAlign = System.Drawing.ContentAlignment.MiddleRight;
this.btnUpdate.UseVisualStyleBackColor = true;
this.btnUpdate.Click += new System.EventHandler(this.btnUpdate_Click);
//
// btnDelete
//
this.btnDelete.Cursor = System.Windows.Forms.Cursors.Hand;
this.btnDelete.Enabled = false;
this.btnDelete.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnDelete.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.btnDelete.ForeColor = System.Drawing.Color.White;
this.btnDelete.Image = global::DMS.Properties.Resources.delete_icon;
this.btnDelete.ImageAlign = System.Drawing.ContentAlignment.MiddleLeft;
this.btnDelete.Location = new System.Drawing.Point(11, 206);
this.btnDelete.Name = "btnDelete";
this.btnDelete.Size = new System.Drawing.Size(119, 59);
this.btnDelete.TabIndex = 18;
this.btnDelete.Text = "&Delete";
64
this.btnDelete.TextAlign = System.Drawing.ContentAlignment.MiddleRight;
this.btnDelete.UseVisualStyleBackColor = true;
this.btnDelete.Click += new System.EventHandler(this.btnDelete_Click);
//
// groupBox1
//
this.groupBox1.Controls.Add(this.dateTimePicker1);
this.groupBox1.Controls.Add(this.txtCustomerID);
this.groupBox1.Controls.Add(this.txtContactNo1);
this.groupBox1.Controls.Add(this.Label4);
this.groupBox1.Controls.Add(this.txtContactNo);
this.groupBox1.Controls.Add(this.txtCustomerName);
this.groupBox1.Controls.Add(this.txtNotes);
this.groupBox1.Controls.Add(this.Label2);
System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, ((byte)(0)));
this.txtItemName.FormattingEnabled = true;
this.txtItemName.Location = new System.Drawing.Point(8, 24);
this.txtItemName.Name = "txtItemName";
this.txtItemName.Size = new System.Drawing.Size(271, 29);
this.txtItemName.TabIndex = 245;
this.txtItemName.SelectedIndexChanged += new
System.EventHandler(this.txtItemName_SelectedIndexChanged);
//
// lblTotal
//
this.lblTotal.AutoSize = true;
this.lblTotal.Font = new System.Drawing.Font("Segoe UI", 20.25F, System.Drawing.FontStyle.Bold,

65
this.lblTotal.ForeColor = System.Drawing.Color.Lime;
this.lblTotal.Location = new System.Drawing.Point(12, 553);
this.lblTotal.Name = "lblTotal";
this.lblTotal.Size = new System.Drawing.Size(167, 37);
this.lblTotal.TabIndex = 244;
this.lblTotal.Text = "Grand Total";
this.lblTotal.TextAlign = System.Drawing.ContentAlignment.MiddleLeft;
//
// btnAdd
//
this.btnAdd.BackColor = System.Drawing.Color.White;
this.btnAdd.FlatStyle = System.Windows.Forms.FlatStyle.Flat;
this.btnAdd.Font = new System.Drawing.Font("Segoe UI", 9.75F, System.Drawing.FontStyle.Regular,

this.btnAdd.ForeColor = System.Drawing.Color.Black;
this.btnAdd.Location = new System.Drawing.Point(853, 553);
this.btnAdd.Name = "btnAdd";
66
6.5 Produce test plans with appropriate test cases to test all aspects of the system (LO 3.1)
The software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive. A strategy for
software testing integrates software test case design methods into a well-planned series of steps
that result in the successful construction of software. Testing is the set of activities that can be
planned in advance and conducted systematically. The underlying motivation of program testing
is to affirm software quality with methods that can economically and effectively apply to both
strategic to both large and small-scale systems.
Software testing
The software engineering process can be viewed as a spiral. Initially system engineering defines
the role of software and leads to software requirement analysis where the information domain,
functions, behavior, performance, constraints and validation criteria for software are established.
Moving inward along the spiral, we come to design and finally to coding. To develop computer
software we spiral in along streamlines that decrease the level of abstraction on each turn.
A strategy for software testing may also be viewed in the context of the spiral. Unit testing begins
at the vertex of the spiral and concentrates on each unit of the software as implemented in source
code. Testing progress by moving outward along the spiral to integration testing, where the focus
is on the design and the construction of the software architecture. Talking another turn on outward
on the spiral we encounter validation testing where requirements established as part of software
requirements analysis are validated against the software that has been constructed. Finally we
arrive at system testing, where the software and other system elements are tested as a whole.
UNIT TESTING
67
MODULE TESTING
Unit Testing
Unit testing focuses verification effort on the smallest unit of software design, the module. The
unit testing we have is white box oriented and some modules the steps are conducted in parallel.
1. WHITE BOX TESTING
This type of testing ensures that

 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.
2. BASIC PATH TESTING
68
Established technique of flow graph with Cyclomatic complexity was used to derive test cases
for all the functions. The main steps in deriving test cases were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:
V(G)=E-N+2 or
V(G)=P+1 or
V(G)=Number Of Regions
Where V(G) is Cyclomatic complexity,

E is the number of edges,
N is the number of flow graph nodes,
P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.
CONDITIONAL TESTING
In this part of the testing each of the conditions were tested to both true and false aspects. And all
the resulting paths were tested. So that each path that may be generate on particular condition is
traced to uncover any possible errors.
DATA FLOW TESTING
This type of testing selects the path of the program according to the location of definition and use
of variables. This kind of testing was used only when some local variable were declared. The
definition-use chain method was used in this type of testing. These were particularly useful in
nested statements.
LOOP TESTING
69
In this type of testing all the loops are tested to all the limits possible. The following exercise was
adopted for all loops:
 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For nested loops test the inner most loop first and then work outwards.
 For concatenated loops the values of dependent loops were set with the help of connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and tested as above.
Each unit has been separately tested by the development team itself and all the input have been
validated.
70
6.6 Carry out complete system testing against the requirement specification; record test
results and rectify any errors and shortcomings in the developed system (LO 3.1) (LO 3.2)
Analyzing Test Cases
Test 01
Test Case Test 1
Test Objective Check whether system allow to enter to correct username and password to
the system
Username = User123 Password = 1234
Test Data
Expected Result Allowing enter to the next Menu
Actual Result The action have been entered – Result ok
Decisions No variation between actual and expected result
Table 2
Test 02
Test Case Test 1
Test Objective Entering wrong password or username to the application for user
Test Data Username = abcsss Password = 124566
Expected Result Show error message and allow to enter again correct username and
password
71
Test 03
Test 1
Test Case
Test Objective Checking Sales Management working correctly
Test Data Authorized Items id can borrow Customers
Expected Result The customer can borrow the Items
Table 3
Test 04
Test Case Test 5
Test Objective Checking Customer Registration function working correctly
Test Data Authorized user enrolled registration
Expected Result Authorized person can reserve as permanent customer
Table 4
72
Test 05
Test Case Test 6
Test Objective Checking the Customer/Items search function is working correctly
Test Data Please enter valid Customer/Items id to search
Expected Result Showing the related Customer ID, Item name, Description, DOB,
.ect……
Table 5
73
6.7 Roll out the system and obtain user feedback (LO 2.3) (LO 3.1)
A questionnaire was distributed to 40 users. The questionnaire was proposed to gather information
about the developed Institute system. Thirty completed questionnaire were returned. I have
received great response from the user provided broad and helpful comment which is reproduced
in following section.
Gender Information
GENDER
Male
40%
Female
60%
Analyze Age group
8-12
AGE GROUP 3%
13-17
9%
40+
24%
25-40 18-24
26% 38%
74
Customer Information
Customer Information
Enrolled
20%
Student
40%
Course
40%
Information about users
Information about Student

No Management System
Knowledg
e
10%
Some
Knowledge Very
25% Knowledgea
ble
65%
75
Each and every system has some limitations that can restrict then to work on a particular
environment. Through our system is provided high amount of accuracy and quick data generation
there is still some limitations that led us to in greater deficiency to work on that system.
 Some of the limitation that is observed during all the process is mentioned below
 This system requires knowledgeable person to use this system.
 The system is not cover the payment collection.
 This system doesn’t provide online payment management.
 The system is Desktop base application (not website) so internet facility must be need.
 This system is a web base system so it may slow when more users accessing same interface
at same time.
 For data storage large number of memory covered by system on web
 User does not view topper of that organization.
 This system is not cover online admission.
Enhancements
 In future our system can include Online Accounting System, Good Backup and Restore
Facility.
 System is so much flexible so in future it can increase easily and new modules can be added
easily.
76
7) Critical appraisal and conclusion (LO 3.3)
My project is only a humble venture to satisfy the needs in TA Enterprises Co” Vehicle Sales and
Purchase organization. Several user friendly coding have also adopted. This package shall prove
to be a powerful package in satisfying all the requirements of the organization.
In Development and connecting multiple database application, when user send the searching
request then application will search the data from those databases in which search data is saved
and return the result from all SQL Database. The objective of Project planning is to provide a
frame work that enables the manger to make reasonable estimates made within a limited time
frame at the beginning of the software project and should be updated regularly as the project
progresses.
7.1 Reflect on your own project work; critically appraise the system (how successful your
solution? Pitfalls, shortcomings etc.)
Every Edition of a book comes with new topics and modifications if any errors are present. In the
similar way, in near future, the application will overcome the flaws if occurred, and attains new
features offered to employees for the Flexible and easy Transportation. Following are the
Enhancements to the application.
 Providing Good User Interface.

 Providing access permissions to the Customers
 Try to Implement the GPS system in the Vehicle services.
77
7.2 Identify possible future extensions of your system
In the past, developers created such applications using C/C++ in conjunction with the Microsoft
Foundation Classes (MFC) or with a rapid application development (RAD) environment such as
Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products
into a single, consistent development environment that drastically simplifies the development of
client applications. The Windows Forms classes contained in the .NET Framework are designed
to be used for GUI development. You can easily create command windows, buttons, menus,
toolbars, and other screen elements with the flexibility necessary to accommodate shifting business
needs.
For example, the .NET Framework provides simple properties to adjust visual attributes associated
with forms. In some cases the underlying operating system does not support changing these
attributes directly, and in these cases the .NET Framework automatically recreates the forms. This
is one of many ways in which the .NET Framework integrates the developer interface, making
coding simpler and more consistent.
8) Presenting and defending the project work
8.1 Record your project work in an appropriate format (refer Final Report Format) (LO
4.1)
The document created based on the scenario mentioned above
78
References
[1] Ahmed, A., Kayis, B., and Amornsawadwatana, S., 2007, "A review of techniques for risk
management in projects": An international Journal, 14(1), pp. 22-36.
[2] Ben-David, I., and Raz, T., 2001. "An integrated approach for risk response development in
project planning": Journal of the Operational Research Society, 52, 14-25.
[3] Berny, J., and Townsend, P., R., F., 1993, "Macrosimulation of project risks - a practical way
forward": Risk Management, (11)4, pp. 201-208.
[4] Bourne, L., and Walker, D.H.T., 2005. "Visualising and mapping stakeholder influence":
Management Decision, 43(5), pp. 649-660.
[5] Clemen, R., T., 1996, Making Hard Decisions: An Introduction to Decision Analysis, New
York, Druxbury Press.
[6] Henley, E.J. and Kumamoto, H., 1991, Probabilistic Risk Assessment: Reliability Engineering,
Design and Analysis, New York, IEEE Press.
[7] Jergeas, G., F., Williamson E., Skulmoski G., J., and Janice T.,
2000. "Stakeholder Management on Construction Projects": AACE International Transaction, pp.

P12.1-P12.6
[8] Karlsen, T., J., 2002. Project Stakeholder Management: Engineering Management Journal,
14(4), pp. 20.
79

PDIE Assignment

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PDIE Assignment

Caricato da

Copyright:

Formati disponibili

Project Design

BTEC HND in Computing and Systems Development

1) Background and Project justification (LO 1.1)......................................................................................... 5

Project will take one and half months

Project manager is responsible to be reported in writing to the Steering Committee

Drawbacks of current design

 Complicated Network Design

1.2 Define the objectives of the project

 Proper network infrastructure.

Direct Stakeholders Indirect Stakeholders

Drawbacks of the existing system

 The network diagram is not available.

 Phase 1: Requirements gathering

Determining of the upgrade and changes may affect the organization.

 Phase 2: Selection and design

 Phase5: Review and Evaluation

 Phase6: User awareness/Training & Education:

 No details available about the method of cabling the network.

3.1 Employ appropriate fact finding techniques to gather requirements

Success criteria factors

 Formulating and planning of the project – A feasibility study could be conducted in

Failure criteria factors

1. No proper planning and preparation

 Final Technical Evaluation (Phase 3)

Admin Cool Cab User

Cool Cab Admin

Id & Password Valid Id &

Level 2 Diagram Maintenance manager

Maintenance Id & Password Valid Id&

Level 2 Diagram Movement manager

Movement Id & Password Valid Id&

But a new system was proposed to overcome the above drawbacks.

Functionalities and advantages of proposed system are:

 Association Employee and shift schedule

 What is the Employee id of an Employee?

Requirement Gathering (Phase 01) Site Visits  ICT Infrastructure.

 What instance would the resource be mostly used?

Prepare a product breakdown structure

Factors to be considered about human resources by the “Project Manager”:

 Efficient allocation of Human Resource.

Project Management Process

Why do projects fail?

 Poor requirements which cannot be tested

6) Implementation and Evaluation

 Senior Project Manager/Project Manager

Project Team Leader

Database Connection Code

public string DBConn = @"Data Source=Nadeeka\SQLEXPRESS;Initial Catalog=DMS; Integrated Security=True";

partial class frmCustomer

/// Required designer variable.

private System.ComponentModel.IContainer components = null;

/// Clean up any resources being used.

protected override void Dispose(bool disposing)

if (disposing && (components != null))

#region Windows Form Designer generated code

/// Required method for Designer support - do not modify

/// the contents of this method with the code editor.

private void InitializeComponent()

this.dateTimePicker1 = new System.Windows.Forms.DateTimePicker();

this.txtCustomerID = new System.Windows.Forms.TextBox();

this.txtContactNo1 = new System.Windows.Forms.TextBox();

this.Label4 = new System.Windows.Forms.Label();

this.txtContactNo = new System.Windows.Forms.TextBox();