Table of Contents Introducti Introduction on .................................. .................................................. ................................. .................................. ................................. ................................. ....................... ...... 2 LO1: Be able to formulate a project ....................................................................................... 3 1.1 Formulate and record possible outline outline project specifications .................. ......... ................... ................... ........... .. 3 1.2 The factors that contribute to the process of project selection................... ......... ................... .................. ........... 7 1.4 Produce an appropriate appropriate project plan plan for the agreed agreed project project ................... .......... ................... ................... ......... 10 LO2: Be able to t o implement the project within agreed procedures and to specification ..... ... 12 2.1 Match resources efficiently to the project ................................................................... 12 2.3 Organise, analyse analyse and interpret relevant relevant outcomes .................. ......... ................... ................... .................. .............. ..... 13 Context Context Diagram Diagram ................................. ................................................. ................................. ................................. .................................. ........................ ...... 13 Data Flow Diagram ...................................................................................................... 14 Initial Entity Relationship Diagram ................................................................................ 15 Normalis Normalisation ation............................... ................................................. .................................. ................................. .................................. ............................. ............ 16 ERD from Normalisation .............................................................................................. 18 Final Final ERD ............................... ................................................ .................................. ................................. .................................. .................................. .................. 19 Entity Entity Grid ............................... ................................................ .................................. .................................. .................................. ................................. .................... .... 20 Entity Event Matrix........................................................................................................... 21 Entity Life History ............................................................................................................ 22 Bibliogra Bibliography phy ................................. ................................................. ................................. .................................. ................................. ................................. ..................... .... 23
Introduction The fundamental nature of a project is that it is a “temporary endeavour undertaken to create a unique unique product, service, or result.” result.” Projects are distinguished from operations and from programs. “Project management is the process of the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.”That requirements.”That is, project management is an interrelated group of processes that enables the project team to achieve a successful project.
LO1: Be able to formulate a project 1.1 Formulate and record possible outline project specifications Project Management Project management is the application of processes, methods, knowledge, skills and experience to achieve the project objectives. General A project is a unique, transient endeavour, undertaken to achieve planned objectives, which could be defined in terms of outputs, outcomes or benefits. A project is usually deemed to be a success if it achieves the objectives according to their acceptance criteria, within an agreed timescale and budget.
The core components of project management are:
defining the reason why a project is necessary;
capturing project requirements, specifying quality of the deliverables, estimating resources and timescales;
preparing a business case to justify the investment;
securing corporate agreement and funding;
developing and implementing a management plan for the project;
leading and motivating the project delivery team;
managing the risks, issues and changes on the project;
monitoring progress against plan;
managing the project budget;
maintaining communications with stakeholders and the project organisation;
provider management;
closing the project in a controlled fashion when appropriat
Project management process group The project management is divided into five individual phases or process. They are initialing, planning, executing, monitoring and controlling and closing. Initiating Process Group The initiating process group involves the processes, activities, and skills needed to effectively define the beginning of a project. Setting all permits, authorizations, and initial work orders in place to secure an effective and logical progression of initial project activities sets the stage for subsequent success throughout all project phases. Setting clear phases for work to be completed, initializing teams, and having the budget in place before work begins are vital for a strong start to any project across industry. Planning Process Group The Planning Process Group sets forth the processes needed to define the scope of the project, set strategic plans in place t o maximize workflow, and begin to assemble priority lists and plan team needs. This process group also addresses a more narrow clarification of all project goals and expectations and puts in place the project infrastructure necessary to achieve those goals according to the timeline and budgetary constraints. Executing Process Group The executing process group involves managing teams effectively while orchestrating timeline expectations and reaching benchmark goals. Project managers utilizing this set of skills will demonstrate a high degree of organization and communication skills while addressing team concerns or other complex situations associated with getting the work done on time and within budget. Monitoring and Control Process Group Processing change orders, addressing on-going budget considerations, and mitigating unforeseen circumstances that may affect a team’s ability to meet initial project expectations are all part of the core skills and competencies involved in the Monitoring Process Group. Seasoned managers keep the momentum moving forward and guard the project against stalling by actively monitoring progress and using foresight and quick response to address project challenges. Closing Process Group Bringing a project to a successful close on time and within budget is no small feat. The Closing Process Group addresses the culmination of strong project management skills demonstrated throughout the other interrelated processes that guided the project. Following
through to close all aspects of the process and submitting necessary paperwork on time is just as important as all other skills and processes.
SDLC for the project of SreeLeathers Mr Masud Ibrahim wants to open 5 retail store and an online store for selling SreeLeathers products. With several store and online store for SreeLeathers, a medium computer based system will need to be developed. So to develop SreeLeathers system waterfall and prototyping mythology could be used. But as SreeLeathers is a leather product shop so the requirement can change with time and a new version of the system may need to be developed in the very future, so using prototyping system development is better to develop a system for SreeLeathers.
As Prototyping allows user involvement with the developer in the development process, so Mr Ibrahim can get the system exactly as he wants for his organization. So, the user of the SreeLeathers system will be more satisfied if the system is developed with prototyping methodology.
Phases of Prototype system development life cycle
Requirement Specification of SreeLeathers There can be many type of requirement it could be functional requirement, not functional or optional and some requirement are hidden requirements. Any system has to be able tp achieve the functional requirements but as non-functional are optional they can be achieved with the next version of the system. But the hidden requirement which can be functional requirement or not functional requirement should be found out and dealt with accordingly. Below types of requirement of SreeLeathers are described. Functional requirement
Ensure the physical security of the warehouses, stores and the leather products
He wants a live inventory management system from which he will be able to monitor his best selling products & their minimum stock and reorder options
Find a way to market his franchised products to the leather market population in Bangladesh
Mr Ibrahim wants an online store for his stores so that his customer and client can buy good from online and get delivered in their house.
Different user needs to have different authentication to access the system.
Every sales history must be preserved for at least 7 years.
He want to keep the customise order option in the system for only his clients.
He wants accurate sales report from the system for every day, every week and every month.
The system has to be a mirror site so that any damage occur the system can be recovered.
Accuracy of the delivery systems of the ordered goods online.
Non-functional requirement:
He wants to store regular customers detail so that he can allow to send the customer special offer via internet and give them certain discounts in every season in Bangladesh.
He wants to deliver the goods to the customer via Sundarban Courier.
He wants to know that how many permanent customers he has and after how long they come to buy the products from SreeLeathers.
He wants to know what the most favoured item is in each store from the system.
Which product is popular in which season in which branch of the store store
The system has to be fast
Online store website has to be fast
Online store has to accept all the payment method
Client registration process has to be easy
There should be an option in the system for the customer feedback and review of the product
Self-payment check requirement
Hidden requirement:
System has to be easy to modify if future needed
The system has to have a backup so that any damage that may occur can be easily restored.
1.2 The factors that contribute to the process of project selection Feasibility reports for the proposed new system Schedule Feasibility Report
The main objective of the schedule feasibility report is to achieve the better delivery of the properly functioning information system later than to deliver an error prone. The work breakdown structure was decided according to the time scale the project is scheduled. On acceptance of the software design the prototype solution could be implemented to the benefit of the company. The software could be upgraded and adjusted to suit the company requirement.
Costs Associated with the New System Development and Purchasing Cost Value/unit
Total price
1.
Hardware
5 HP bubble jet printers
5,000
25,000
4 Core i5 computers
35,000
140,000
10 Black & White cartridges
5,000
5,000
ADSL routers & Wi-Fi routers
20,000 190,000
TOTAL
2.
Software
Operating system(Windows 8.1)
9,000
9,000
TOTAL
3.
9,000
network connectivity
5m network cable
100
500
1,000
Installing chargers
5,000
TOTAL
5,500
4.
development costs
80,000
5.
Domain registration
1000
Grand TOTAL
285,500
Maintenance costs Implementations
value/unit
Total
5,000
25,000
15,000
75,000
5,000
5,000
2,000
2,000
Maintenance
Service and upgrading of hardware Servicing and upgrading software
Maintaining networks
Web host fees
TOTAL
107,000
Salaries
5 store Manager
20,000
100,000
15 Store Keepers
8,000
120,000
Warehouse caretaker
6,000
6,000
6 Security Personnel
5,000
30,000
TOTAL
256,000
TOTAL Monthly
363,000
1.3 Project Charter
1.4 Produce an appropriate project plan for the agreed project System Development Life Cycle (SDLC) I will be using the prototyping system development life cycle to develop the new system for SreeLeathers. The SDLC will be running each processes of PMI project management system using the Deming cycle model on each phase. Initial Study & Analysis
SU
MP
IP CS
PL
SB DP CP
Figure: The SDLC model
Implementation
Milestones of completing the SDLC Phase No.
Phase Name
Deliverables
Duration
A
Initial Study & Analysis
2
B
Planning
1
C
Starting Up a Project
1
D
Initiating a project
2
E
Controlling a Stage
2
F
Managing Stage Boundaries
2
G
Managing Product Delivery
3
H
Directing a Project
2
I
Closing a Project
1
Start Date
End Date
LO2: Be able to implement the project within agreed procedures and to specification 2.1 Match resources efficiently to the project Phase No.
A B C
D
E
Phase Name
Background Study Planning Starting Up a Project Initiating
a
project Controlling a Stage
Deliverabl es
Duration
Start
End
Phase
Resource
Date
Date
Dependencies
Allocation
2
-
1
A
1
B
2
B, H
2
G, H
2
B, H
3
E
2
C, D, E, F, H
1
H
Managing F
Stage Boundaries Managing
G
Product Delivery
H
I
Directing
a
Project Closing Project
a
2.3 Organise, analyse and interpret relevant outcomes Context Diagram
At first we have to draw the context diagram of the system to be built. A context diagram is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it. This diagram is a high level view of the system.
Delivery
Supplier
Employee
Note
Payslip
Order
Supplier Details
SreeLeathers System
Sales
Purchase
Payment Invoice/Bill
Order
Retrieve purchase detail
&product Customer
Customer
(Store)
(Online) Figure: Context Diagram of SreeLeathers
The diagram shows the external entities and data flows into and out of the system.
Data Flow Diagram
1
Order
Customer
Order Product
Bill
Orders Inventory details
D
D
Inventory Inventory details
Order
Orders
2
Inventory details
Reports
Generate
Employee
Re orts
3
Inventory Order
Order Inventory
Supplier Inventory Order
Figure: Data Flow Diagram The above Data Flow Diagram contains three processes, three external entities and two data stores. Based on the diagram, we know that a Customer can place an Order . The Order Product process receives the Order , store it in the Order data store, and store the updated Inventory details in the Inventory data store. The process also delivers a Bill to the Customer . Employee can takes Inventory
receive Reports through details and Orders as
the Generate
input from
Reports process,
the Inventory and Order data
which store
respectively. Employee can also initiate the Order Inventory process by providing Inventory order . The process forwards the Inventory order to the Supplier and stores the updated Inventory details in the Inventory data store.
Initial Entity Relationship Diagram
In accordance to our approach of sandwich method we will first create an initial Entity relationship diagram (ERD) and then create a ERD from Normalisation. We will compare the two ERDs and then we create the final ERD to be used. Entity relationship diagram is a visual presentation of link between entities. An entity is an object that exists and which is distinguishable from other objects.
Sales
Customers
Employees Sales Details
Products
Figure: ERD of SreeLeathers
Normalisation
To do normalisation of SreeLeathers we will use a receipt of the business. We will use the information generated from the receipt to do our normalisation.
SreeLeathers Sale id:
31, Road 5, Dhanmondi, Dhaka, Bangladesh
TOTAL
Contact: 01911111111
Figure: Screenshot of the receipt
We have created a normalisation table from the information available from the receipt.
Normalization of SreeLeathers UNF
1NF
2NF
3NF
Sales_ID
Sales_ID
Sales_ID
Sales_ID
Company_ID
Company_ID
Company_ID
Company_ID*
Company_Name
Company_Name
Company_Name
Customer_ID*
Company_Address
Company_Address
Company_Address
Employee_ID*
Sales_Date
Company_Phone
Company_Phone
Sales_Date
Sales_Total
Sales_Date
Customer_ID
Sales_Total
Customer_ID
Sales_Total
Customer_Name
Customer_Name
Customer_ID
Customer_Address
Company_ID
Customer_Address
Customer_Name
Sales_Date
Company_Name
Product_ID
Customer_Address
Sales_Total
Company_Address
Product_Name
Entities
Sales
Companies
Company_Phone
Product_Details
Sales_ID
Product_Quentity
Product_ID
Sales_ID
Customer_ID
Product_Price
Product_Name
Product_ID*
Customer_Name
Sub_Total
Product_Details
Product_Quantity
Customer_Address
Company_Phone
Product_Quantity
Sub_Total
Customers
Product_Price Sub_Total
Product_ID
Sales_ID
Product_Name
Product_ID*
Employee_ID
Product_Details
Product_Quantity
Employee_Name
Product_Price
Sub_Total
Product_ID Employee_ID
Product_Name
Employee_Name
Product_Details
Sales Details
Products
Product_Price
Employee_ID Employee_Name
Employees
ERD from Normalisation
After the completion of Normalisation we have got the following ERD. Companies
Sales
Employees
Customers Sales Details
Products
Figure: ERD from Normalisation
As we can see a new entity has derived from the normalisation process.
Final ERD
Our final ERD is same as the normalisation ERD as it contains all needed entities and relationships to create our database system.
Companies
Sales
Employees
Customers Sales Details
Products
Figure: Final ERD
Entity Grid Companies
Employee
Sales
Sales
Products
Customers
Details Companies
X
Employees
X
Sales
Sales Details Products
Customers
X
X
X
Entity Event Matrix Event \ Entity Companies
Employees
Sales
Sales Details
Order
C
C
Delete_Order
D
D
Products
M
C
C_Registration
Product_Entry
C
Products_Price_Change
M
C
Employee_Registration
Company_Contact_Change
Customers
M
Chart: C= Create
Figure: Entity Event Matrix
M= Modify D = Delete
Entity Life History
Product
Start
Delete_supply
Product Mid-life
Supply
Seek_order
(new)
(new)
Order
Supply
Tender_order (new) Tender_notice
Seek_order (old)
Order_payment
Confirm_order
Figure: ELH of Product
Purchase_goods
Bibliography PDF: 1. Đurković, O. and Raković, L. (2009). Risks in Information Systems Development Projects. 4th ed. [ebook] University of Novi Sad. Available at: http://www.ef.uns.ac.rs/mis/archivepdf/2009%20-%20No1/MIS2009_1_3.pdf [Accessed 19 Feb. 2016]. 2. Nikolić, B. and Ružić-Dimitrijević, L. (2009). Risk Assessment of Information Technology Systems. 6th ed. [ebook] The Higher Education Technical School of Professional Studies.
Available at: http://iisit.org/Vol6/IISITv6p595-615Nikolic673.pdf [Accessed 19 Feb. 2016]. 3. Radack, S. (2009). 1st ed. [ebook] National Institute of Standards and Technology. Available at:
http://csrc.nist.gov/publications/nistbul/april2009_system-development-life-cycle.pdf
[Accessed 19 Feb. 2016].
Websites: 1. Fdic.gov, (2016). FDIC: Risk Assessment Tools and Practices for Information System Security . [online]
Available
at:
https://www.fdic.gov/news/news/financial/1999/fil9968a.html
[Accessed 19 Feb. 2016]. 2. Sans.org,
(2016).
[online]
Available
at:
https://www.sans.org/reading-
room/whitepapers/auditing/introduction-information-system-risk-management-1204 [Accessed 19 Feb. 2016].
