A Partial Fulfilment of Final Examination of Software Project Management
A Partial Fulfilment of Final Examination of Software Project Management
Submitted to:
The
Technology
Submitted By:
Ranjita Maharjan
Roll No.:7
BCA 7 sem
Submitted to:
Sudarshan Sharma
January 2023
TRIBHUVAN UNIVERSITY
FACULTY OF HUMANITIES & SOCIAL SCIENCE
NAGARJUNA COLLEGE OF INFORMATION
TECHNOLOGY
We certify that “this project is satisfactory in the scope and use of computer
application in the practical fulfilment for the requirement of BCA 7th
semester of Software Project Management”.
Evaluation Committee
Lab: 1 Planning
The project plan describes the cost, scope, and schedule for the project. It lays out exactly what
activities and tasks will be required, as well as the resources needed, from personnel to equipment
to financing, and where they can be acquired. Good project planning also factors in risk and how
to manage it, including contingency plans, and details a communication strategy to keep all
stakeholders up to date and on board.
1. Project Selection:
This project is “E commerce System” for online seller and buyer. This system provides the
advantages of online shopping to customers as a real shop. Online shopping system, customer
need not go to the shop for buying the products. Customer can order the product he/she wishes to
buy through the application in Smart Phone .It helps buying the products in the shop anywhere
through internet. The user can add the desired product into his cart by clicking add to cart option
on the product. He can view his cart by clicking on the cart button. All products added by cart can
be view in the cart. User can remove an item from the cart by clicking remove.
After confirming the items in the cart the user can submit the cart by providing a delivery address.
On successful submitting the cart will become empty. Thus the customer will get the service of
online shopping and home delivery from his favorite shop.
3.Analysis
The requirement analysis consists of two basic requirements i.e. functional and non-function
requirement which are listed below:-
Functional Requirement
For user
User Login,logout
Registration new user
Purchasing an Item
add to cart
make a payment
For admin
User Login,logout
Manage order
Manage product
Manage User
Non-Functional Requirement
Security:
Usability
5. Risk Occurred:
Staff may drop the project
Estimate budget is not enough
Client may drop the project.
Maintain cost higher then Estimated
Competitor undercut prices
6. Allocated Resource
Many resource are allocated for developing the whole project Resource like human resource that
is team leader, front end developer, back end developer, QA, Business Analyst. Technical
Resource may be hardware ,software, etc
Lab:2 Risk Management
Different risk may occurred in our time-frame risk may be:
Risk Exposure = Probability * Impact
where, probability mean chance of risk occurred and impact in the project.
As our task list is in its normal state, no tasks can be outdented. We can create subtasks by
indenting the desired tasks. When we indent a task, it becomes the subtask of the task above it.
The more a task is indented the more its hierarchy decreases.
1.3 Defining duration, start & end dates
Defining start date and finish date are similar processes with a.
Click on the start or finish date, then you can either enter the date manually or select one
from the date picker.
After, selecting the start and end date, the duration will be automatically calculated based
on the work-time provided.
An alternative way of entering start and finish is to enter one of them and enter the
estimated duration required to complete the task and the corresponding date will be
automatically updated.
After assigning start and finish date for all of the tasks, the gantt chart will be created on
the right hand side as shown in the figure below.
After clicking on Add New Column, we will get a list of options to choose from; among them we
choose the Priority option to create a new column for Priority.
After the priority column is created, we can provide desired priority points to each task as
required.
Adding priority does not bring any changes to the Gantt chart.
Now, we add the resources by filling in the necessary details related to the resource. For this lab
work, we used employees as resources and after entering required data, it looks like the following:
The sheet shows the list of available resources during the project along with their respective
details.
Now, we again choose Gantt chart from the view menu options and input desired resource names
for each task in the Resource Names column. We can also assign multiple resources to a single
task. After the resource allocation, our sheets look as following:
4: Defining and Adjusting Work Time
To make any changes related to work time, we go to the Project tab on the menu bar. Then we
click on Change Working Time. This opens up a dialog box named ‘Change Working Time,’
where we can manage, edit or adjust anything related to the work time of the project.
In the chart, the dark line in the task bar represent task progress.
After we tick the desired options, the output shows in Gantt chart.
In above Gantt chart, the task bar with stars at its start and end are the critical tasks and the task
bar with circled down symbol are late tasks. Similarly, the lines that extend for some taskbars are
slack.
7: Generating Report
Preparing reports is also an easy tasks with the feature of Microsoft Project. To prepare report, we
go to Report menu then select the desired report. The report can be an overview report or related
to resources, costs or progress.
For finding critical path, we just enter the given details on Project sheet as follows:
Here, the darker shades represent critical path. Hence, the critical path is 1→2→4→7→9→10.
Numerical 2:
Activity Preceding Activity Duration(days)
A - 3
B A 5
C A 2
D B 5
E C 1
F C 2
G D,E 4
H F,G 3
Hence, the critical path is 1->2->4->7->8 or A→B→D→G→H.
Lab 4:
Git and Github
Git and GitHub are two different entities that help you manage and host files. In other
words, Git serves to control file versions while GitHub is a platform for hosting Git
repositories.
1. git status
While working on git, we need to know what the state of our folders, files and
repositories. This details are provided by ‘git status’
2. git init
Before doing anything on git, we first have to create a repository and git init allows us to
do so.
When we first check git status on a random folder on our PC, we get the message that it is
not a repository. Hence any work done here is not stored on the GitHub. So, the first step
is to make the folder a repository using ‘git init.’
Here, ‘git init’ has create a local repository on our PC. Now if we use git init, it gives us
details on the files present on our repositories.
This opens up a form asking for details regarding the new repository like the following:
In the ‘Repository name’ it is suggested to provide the project name for convenience and
effectiveness. After filling the form, click the ‘Create repository’ button and our remote
repository is ready. Now, we add the local repository to the remote repository using git
remote add origin <…>.
Here, ‘origin’ is the name of the remote repository and
‘[email protected]:ranjita088/excel_file.git’ is the link to the repository.
4. git remote
We use git remote, to check the available or connected remote repositories.
We have now added or staged the file ‘tings to do.txt’ for the repository. The results can
be seen after using git status. However, the file is still not tracked or present on the
repository.
6. git commit
After files or changes are finalized and are ready to be added to the main source or remote
repository. They are committed using git commit. This means the files are now added to
the repository. But it is still only on the local repository.
Here, -m is an argument used to pass message related to the changes we are saving or
committing. This case the message or remarks is “things to do.”
Here, ‘origin’ is the name of the remote repository and ‘master’ is the name of local
repository. Hence, the command git push –u origin master means pushing the files and
changes to the repository named ‘origin’ from the local repository named ‘master’