Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
• Project Planning:
• Objectives Of System:
Computer system makes it easy to maintain book record than traditional system.
1) Notification when the stock of the book falls below the recorded level.
8) There is less time difference in the order placement & carrying out of the order.
10) Reports can be generated easily & graphically as & when needed.
11) Important data can be provided proper security for restricted access.
12) The data can be backed up easily by using some kind of a removable drive, which
makes the system more reliable.
• Internal Guide:
Mr. XYZ
• Team Size:
1 Person
1. Project Planning
2. Project Scheduling
3. Risk Management
PROJECT PLANNING :
NAME BOOKS ORDERING SYSTEM
Project Objectives This project is developed in computer
system is for storing, maintaining all the
order of books , payment details , purchase
order etc.
Project Execution Model Waterfall Model
Internal Guide Mr. XYZ
Team Size 1 member
Duration 2-1/2 month
PROJECT SCHEDULING :
• Timeline Chart :
WEEK 1:
WEEK 2:
4 Data Dictionary
related to project
5 Data Dictionary
related to project
WEEK 3:
No. Tasks Day-1 Day-2 Day-3 Day-4 Day-5
1 Design Home
Page
WEEK 4:
WEEK 5:
3 Design feedback
form
WEEK 6:
2 Coding about
different forms
like order, pay
details etc.
3 Design feedback
form
WEEK 7:
WEEK 8:
• Risk Management
Simplest and possibly best definition of risk is “the possibility of loss injury,
disadvantage or destruction.
Risks are of many types:
1. Programmatic risk
2. Schedule risk
3. Cost risk
4. Technical risk
5. Supportability risk
Risk management is the sum of all proactive management directed activities
within a program.
o Risk Identification
The purpose of this topic is to identify the risks involved in project. Here we will
consider all the possible risks that can affect the project. All such risks are
involved below. Due to some technical or managerial reason the project might not
be able to meet its requirement up to ultimate data given. This risk exists in almost
all the projects. Technology being used might not be able to meet the expectation.
This can occur when the design of some processes cannot be implemented in the
chosen programming language.
Developer inexperience is also one of the risks which will be considered. This
might happen if the person who chooses for one particular task has no experience
in doing similar work. Constant turnover might happen. The possibility of the risk
is hard to gauge. If developer turnover is high then there will be a very high
negative impact on the project. This also delay the project as new people will first
have to understand what is happening and the flow of the module. Database crash
is one of the technical risks that will be considered. This risk will be prioritized
first.
Risk Analysis
Risk analysis is a systematic approach for describing and/or calculating risk.
During risk analysis process, each identified risk is considered in term and a
judgment made about the probability and the seriousness of the risk.
1. The probability of the risk might be assessed as very low (less than 10%), low
(10-25%), moderate (25-50%), high (50-75%) or very high (greater than
75%).
2. The effects of the risk might be assessed as catastrophic, serious, tolerable or
insignificant.