Mobile/Web App Development Project Report

of 27
Introduction
Every day a human being has to go somewhere for some reason Because of some important work at home
or someone job work or because of visiting somewhere, and when they get there they get in trouble like
due to weather error or other technical error and there is no one to help them
Now, we are going to provide you a platform in the form of mobile application where you can that can help
you with problems.
ProjectPlanning
The plan for all software development shall employ software engineering „best‟
practices in verification and validation, configuration management, peer reviews, project tracking and
oversight, and software quality assurance. The build project plans will be made available to all participants.
The Software Project Manager will use weekly project wide meetings to maintain the status of the software
project and to resolve any conflicts or changes that might occur. The project aimed to build a fully
functional system in order to achieve the efficiency.The Software Project Manager will employ a
database to record action item assignments, status, and resolutions.
Purpose:
In our daily life we have to go out somewhere for some reason.And especially for females in
our society.Everyone feels that females feelinsecure if they go out.Because we think that they will do if
they are in critical situation or got into trouble.
Now we are going to provide you a mobile application by using which they can share their location send
message for help to friends family members or security agency on single tap.
Scope Management
i)Android Application
It is a Android application that will operate on both customer and admin end.
Scope & Features
• User can get immediate help

of 27
• Get location of user
• Voice Recording Button
• Text message
In today's world, people using smart phones have increased rapidly and hence, a smart phone can be used
efficiently for personal security or various other protection purposes. The heinous incident that outraged the
entire nation have waken us to go for the safety issues and so a host of new apps have been developed to
provide security systems to women via their phones. This paper presents Human security application, an
Android Application for the Safety of Women and this app can be activated this app by a single click,
whenever need arises. A single click on this app identifies the location of place through GPS and sends a
message comprising this location URL to the registered contacts and also call on the first registered contact to
help the one in dangerous situations. The unique feature of this application is to send the message to the
registered contacts continuously for every five minutes until the " stop " button in the application is clicked.
Continuous location tracking information via SMS helps to find the location of the victim quickly and can be
rescued safely.
Objectives: In our Country, even though it has super power and an economic development, but still there are
many crimes against women. The atrocities against the women can be brought to an end with the help of our
product "Human security Application". This device is a security system, specially designed for women in
distress. Method/Analysis.
OS support
Unless otherwise agreed, we will target the iPhone and the three most popular Android smartphones at the
time of development, and build apps that operate in portrait mode only. If you need to support other devices
such as tablets, or need support for landscape mode, we can provide a separate estimate for that.
Our apps are built to run on the following OS versions:
iOS 10 & 11 Android 5-8
The app may also work on other versions of the iOS and Android Operating Systems, but we won't
test on other versions. We also cannot guarantee that the app will function correctly in future versions of
the Operating System, but if a defect is found in the future, we can provide a separate estimate for fixing
the defect.
Project Estimation
Cost Estimation
Source of COCOMO :
We get the KLC from React Native.
KLC > Visual Studio > Code Analysis (Options)

of 27
15.2 COCOMO (Barry Boehm):
Organic:
Effort cost:
KLOC = 6100/1000 = 6.1
Formula:
Effort (E) = ab *(KLOC)^bb where (ab= 2.4, bb= 1.05)
E = 2.4 *(6.1) ^1.05
E = 2.4 * (6.6)
E = 15.84 PM (Person Month)
Development Time:
Formula:
Development time (D) = cb* (Effort)^db where (cb=2.5, db=0.38)
D = 2.5 * (15.84) ^ 0.38
D = 2.5 * (2.85)
D = 7.125 (Month Approx.)
Number of People needed:
Team Size= PM/ D = 15.84/ 7.125
Team size= 2.2 (approximately 2)
Team size = 2 people
Development Cost:
Developer rate 50 p/hr.
Cost= 2* 240Hrs/m. *50 Rs.

of 27
Cost for one month= 24,000 Rs.
Cost of Development = 24,000 * 7.125 = 171000 Rs.
FEES, EXPENSES, AND PAYMENT
We’re sure you understand how important it is as a small business that you pay the invoices that we send
you promptly. With this in mind, you agree to stick tight to the payment schedule that is explained below.
Payment Schedule
Project milestone Payment
(cash PKR)
Advance Rs.30,000-/
SRS Rs.10,000-/
User Interface(UI) / Design Rs.50,000-/
Beta Version Rs.50,000-/
Final Delivery Rs.31,000-/
+
Modification(if any)
4.5
Human Resources Estimation
Staff Organization & Team Structure
We uses the egoless (democratic) model for team structuring:
TABLE 7-2. PERSONNEL REQUIREMENTS (PERSON YRS)

of 27
Activity
Personnel
System Rqmts
Analysis/Desig
n
Detailed
Design
Code and
Unit Test
System
Integration
Subtotals
Management 1 2 2 1 6
S/W Engineer 2 2 3 2 9
CM 1 1 2 1 5
SQA 1 1 1 1 4
Testing 1 2 1 3 7
IV&V 1 2 2 2 7
Facilities 1 1 1 1 4
Subtotals 8 11 12 11 (Total) 42

of 27
Project Scheduliding and Resource Management
This section shall present the items listed below: a. Schedule(s) identifying the activities in each build and
showing initiation of each activity, availability of draft and final deliverables and other milestones, and
completion of each activity.

of 27
______Fig: 0.2______

of 27
Consider the use the following resources in software development:
1. Time (Mentioned Above)
2. Human Resources – the most crucial of all the resources
3. Computer Resources
4. Money
Human Resources
Staff Organization & Team Structure
We uses the egoless (democratic) model for team structuring:
TABLE 7-2. PERSONNEL REQUIREMENTS (PERSON YRS)
Activity
Personnel
System Rqmts
Analysis/Desig
n
Detailed
Design
Code and
Unit Test
System
Integration
Subtotals
Management 1 2 2 1 6
S/W Engineer 2 2 3 2 9
CM 1 1 2 1 5
SQA 1 1 1 1 4
Testing 1 2 1 3 7
IV&V 1 2 2 2 7
Facilities 1 1 1 1 4
Subtotals 8 11 12 11 (Total) 42
Role Definitions
 Zeshan Ahmed
Project Manager: Is The the Head of the Current Project (Women Security
App)
 Kashif
Lead Native Programmer:
Kashif is the complete React Native and React Js programmer, with the
exception of Sound Remixing. This includes all logic programming.
Lead Engine Designer: Kashif is also the primary engine designer.
Interface Designer: Kashif is part of the interface design team.

of 27
Documentation: Kashif is responsible for much of the required documentation.
Additional Responsibilities: Kashif is also the primary consultant for Jazib on
Sound issues, and for M. Abubakr on interface design issues.
 Jazib Ahmed
Assistant Programmer: Jazib is coding the Chatting and Calling Module. He is
also managing Audio Sound portion of the app (Remixing).
Engine Designer: Jazib is part of the engine design team.
Interface Designer: Jazib is part of the interface design team.
Documentation: Jon is responsible for much of the required documentation.
 Muhammad Abubakr
Lead Backend Programmer:(Core Php Dev.) Abubakr is the complete
interface programmer, including all database (SQL) programming.
Interface Designer: Abubakr is part of the interface design team.
Documentation: Abubakr is responsible for much of the required
documentation.
 Bilal Warraich
Core PHP Developer: Bilal is Perform very Good Software Testing with.
Documentation Bill is responsible for much of the required documentation.
Computer Hardware Resource Utilization
Computer resource utilization must focus on two constraints; those effecting production in the
development environment, and those impacting the operational user‟s environment. The
following paragraphs address each issue:
a.
Development Environment - The Software Project Manager will establish and maintain a detailed
schedule for computer hardware resource utilization that identifies anticipated
users,purposes, and scheduled time to support analysis, software design, coding,
integration, testing, and documentation. It will address sharing of resources by multiple
users and workarounds to resolve conflicts and equipment downtime. If computer
hardware resource scheduling requires supplementing, potential sources of computer
hardware resources including other SSC San Diego projects or commercial vendors will
be identified. The Software Project Manager will coordinate resource needs with
development, integration, and test groups.

of 27
b.
Operational Users Environment - The Software Project Manager will establish and
maintain a database of the site-specific computer hardware and commercial software
resources. It will address resources by hardware configurations and commercial software
licensing requirements. If a specific site‟s computer hardware resource or licensing needs
are insufficient for a planned build then those needs will be communicated to those site
notifying them of the configuration enhancements needed for the next build.
TestInformation
Test type
Each Possible Case Test, Unit Test,Component Test, Acceptance Testing,SystemTesting
System Under Test
System name: ______Women Security Application______
Version: _____0.1_____ of the configuration here
Test Personnel
Name: _______Bilal_____ Date: ____26-Mar-2020____ Time/h: ____2:00 Hours______
Name: ___Abubakr______ Date: ____03-Apr-2020_____ Time/h: ____3:00 Hours______
Name: ____Bila------_____ Date: ____09-Apr-2020_____ Time/h: ____5::30 Hours______
TestSummary
Results
Conclusion of the test: PASS / FAIL
Identifiers of the observations recorded:
Although Application is Working Properly. Test Failed Does Not means The Women Security App Is Working
Unwell.
___________ ____________ ____________ ____________ _____________
Total number of cases failed: _____12________

of 27
Background
Purpose and Scope ofthe Test
Explain what is going to be tested in this test procedure and what are the requirements covered,
where the requirementscan be found.
Additional Information
This is the place where you can tell where the manuals or other user instructions can be found.
If there is something special(e.g.known bug that cannot be fixed) in the software that you want to
tell the tester, it can be told here.
Preparing the TestEnvironment
Application Setup
Explain the needed configuration and how to set it up. Also, explain operations and steps to reach
the normal start condition for the cases.
Equipment Checks
Possible checksthat hasto be done to verify that the Application is functional before the tests can
be started.
S# Action Input Value Expected Results Actual Results P/
F
Test
Commen
t
7.1.1 Submit Registration
request…
First Name = blank,
Other fields valid
Error message shouldbe displayed
for invalidFirst Name.
Error message
displayed. invalid
First Name.
p Targeted
Input field
Highlighted
request…
Last Name = blank,
Other fields valid
for invalidLast Name.
Error message
displayed. invalid
Last Name.
p Targeted
Input field
Highlighted
request…
Email = blank,
Other fields valid
for invalidEmail.
Error message
displayed. invalid
Email.
p Targeted
Input field
Highlighted
request…
Phone number = blank,
Other fields valid
for invalidPhone number.
Error message
displayed. invalid
Phone.
p Targeted
Input field
Highlighted
request…
Password= blank,
Other fields valid
for invalidPassword.
Error message
displayedinvalid
Password
p Targeted
Input field
Highlighted
request…
Confirm Password= blank Error message shouldbe displayed
for invalidconfirmation password
Pleas Fill All Fields p Targeted
Input field
Highlighted

of 27
1 Test cases
We are testing the login functionality of Women Safety Mobile application. Below are the test cases for the Login
Activity:
1.1 Test Item: Registration Request Form.
Scope: Test various field input on the Registration Request Form.
Action: Submit Registration request.
Test Notes and Preconditions: Open the userregistration request formfromthe userstab.
Verification Steps: Verify the userhas been registered with the given details.
Scenario 1: Test leaving a required field blank on the new user registration
Scenario 2: Test minimum number of characters accepted foreach field.
S# Action Input Value Expected Results Actual Results P/F Test
Comme
nt
request…
First Name = max chars
Last Name = max chars
Email = max chars incl @
Phone # = maxchars
User ID = max chars
Password= max chars
Confirm pwd= max chars
Registrationrequest should
be accepted.
Case Accepted
p
N/A
request…
(Bug#10224)
First Name = max chars
Last Name = max chars
Email = max chars incl @
Phone # = maxchars
User ID = max chars
be accepted.
Case Accepted p N/A
Other fields valid
request…
All fields blank Error message shouldbe displayed. Error: Pleas Fill All
Fields
p Popup
Confirmatio
n Message
Displayed

of 27
Comme
nt
Password= max chars
Confirm pwd= max chars
Scenario 3: Test maximum number of characters accepted for each field.
Comment
7.1.15 Submit Registration request… First Name = 1 char
Last Name = 1 char
Email = a@a.com
Phone # = 1 char
User ID = 1 char
Password= 6 chars
Confirm pwd= 6 chars
be accepted.
InvalidInput
Pleas fill all fields
Properly
F Name, Email,
Password
Cant be a
Single
Character
Login as Admin anddelete this
user…
None User is deleted.
Test Notes & Preconditions: Field input should limit the user to some maximumvalue. If not, an error
should be produced.
Scenario 4: Test exceeding maximumfield input lengths on the new userregistration form.
S# Action Input Value Expected Results Actual
Results
P/F Test
Comment
request…
Enter all special chars in each
field, i.e. `~! @#$%^&*()-
=_+[]{}|;’”<>/?
Except for Email andUser
ID, which shouldbe some
validentry for this test.
be accepted.
Error Appears F Phone Number
Cant Contain
Special
Characters
request…
Enter poundcharin each
field, i.e.
Asd##ads32%^&*(
be accepted.
Error Appears F Phone Number
Cant Contain
Special
Characters

of 27
Scenario 5: Test special characters on the newuserregistration form. This test is for all fieldsexcept
Email and User ID, which are addressed separately.
Scenario 6: Test Email field input.
Except for Email andUser
ID, which should be some
validentry for this test.
S# Action Input Value Expected Results Actual Results P/F Test Comment
request…
Email = a Appropriate error
shouldbe displayed
sayingthe email is
invalid.
Error Appears InvalidEmail
request…
Email = a.b Appropriate error
shouldbe displayed
sayingthe email is
invalid.
request…
Email = a@b Appropriate error
shouldbe displayed
sayingthe email is
invalid.
request…
Email = a@b.c Email address shouldbe
accepted.
Error Appears F InvalidEmail
request…
Email = a@b.com Email address shouldbe
accepted.
Accepted P Accepted
request…
Email = a@.com Appropriate error
shouldbe displayed
sayingthe email is
invalid.
Error Appears P
request…
Email = a_b@c.com Appropriate error
shouldbe displayed
sayingthe email is
invalid.
Error Appears P Spaces Are Not Allowed
request…
Email = a b@c.com Email address shouldbe
accepted.
Error Appears F Spaces Are Not Allowed
request…
Email = a b @c.com Email address shouldbe
accepted.
Error Appears Spaces Are Not Allowed
request…
Email = a@b@c.com Appropriate error
shouldbe displayed
sayingthe email is
invalid.
Error Appears p InvalidEmail
request…
Email =
a`~!@#$%^&*()-
=_+[]{}|;’:”,.<>/?
Appropriate error
shouldbe displayed
sayingthe email is
invalid.
Error Appears p Cant Contain Special
Characters

of 27
Test Notes & Preconditions: The User ID can only contain numbersand letters.
Scenario 7: Test User ID field input.
Comment
request…
User ID = all letters Input shouldbe
accepted.
Accepted P User ID Can BE
OF Characters And
Digits
request…
User ID = all numbers Input shouldbe
accepted.
Accepted P N/A
request…
User ID = alpha-numeric mix Input shouldbe
accepted.
Accepted P N/A
request…
User ID = contains a space
char
Input shouldbe
accepted.
Accepted P N/A
request…
User ID = contains a period. Input shouldbe
accepted(user idmust
be begin with an alpha-
numeric char).
Rejected F User ID Cant
Contains Special
Characters
request…
User ID = contains a dash - Input shouldbe
be begin with an alpha
Contains Special
Characters
request…
User ID = contains a plus char
+
Input shouldbe
be begin with an alpha
Contains Special
Characters
Scenario 8: Password field testsare exercised in the TestCase_TPAS.doc test case document.
1.2 Test Item: Admin Login
Scope: Test valid and invalid login attemptsto the Administration page.
Action: User submits Login form.
Test Notes and Preconditions: Open the admin login page.
Verification Steps: Verify the userhas been entered in to the admin page aftergiven the correct details.
Scenario 1: Test User ID field input.
Results
P/F Test Comment
7.2.1 Admin User submits
Login form
(Bug#10455)
User Name=Invalid It shoulddisplay an error
message saying“The
User ID or Passwordyou
enteredis invalid. Please
try again”
The User ID or
Passwordyou
enteredis invalid.
Please try again
P InvalidEmail and
Password

of 27
Results
P/F Test Comment
Password=Invalid
7.2.2 Click on ‘try again’
hyper link (Bug#
10455)
SRC admin login page
shouldbe displayed
Login Page
Displayed
P InvalidEmail and
Password
Login form
(Bug#10455)
User Name=valid
Password=Invalid
It shoulddisplay an error
try again”
InvalidPassword P InvalidPassword
Login form
(Bug#10455)
User Name=Invalid
Password=valid
It shoulddisplay an error
try again”
InvalidEmail
Address
P Email Must be registered
First
Login forrm
Password= Valid
User Name=valid
Admin user shouldbe
logged in successfully in
the admin page
logged in
successfully
P Login anf Go To Home
Page
1.3 Test Item: Create User.
Scope: Test various field input on the Create User Form.
Action: Submit Create Userform.
Test Notes and Preconditions: Open the User registration formfromthe users tab.
Verification Steps: Verify the userhas been registered with the given details.
Scenario 1: Test various field input on the Create User Form
Results
P/F Test Comment
7.3.1 Submit Create User
form…Admin
First Name = blank,
Other fields valid
Error message shouldbe
displayedfor invalidFirst
Name.
Error message
shouldbe
displayedfor
invalidFirst
Name.
P Enter Valid
Details
form…Admin
Last Name = blank,
Other fields valid
displayedfor invalidLast
Name.
Error message
shouldbe
displayedfor
invalidFirst
Name.
P Enter ValidDetails
form…Admin
Email = blank,
Other fields valid
displayedfor invalid
Email.
Error message
shouldbe
displayedfor
invalidFirst
Name.

of 27
Same Process as Login Case Test Has been Followed For Create, Edit And Delete Users.
And All Cases Accepted.
2 Functional Testing
After conducted the unit testing, functional testing will begin to test the developed system.
Functional testing is performed to verify that the system application processes that perform and
functioning appropriately according to the design specifications. In functional testing, the core
system application functions will be tested with severaltest cases in order to ensure that the entire
system functioning as a whole and perform task that with the expected results.
form…Admin
User ID = blank,
Other fields valid
Error message should be
displayedfor invalidUser
ID.
Error message
shouldbe
displayedfor
invalidFirst
Name.
form…Admin
Password= blank,
Other fields valid
Password.
Error message
shouldbe
displayedfor
invalidFirst
Name.
form…Admin
Confirm Password=
blank
Other fields valid
confirmationpassword
Error message
shouldbe
displayedfor
invalidFirst
Name.
form…Admin
All fields blank Error message shouldbe
displayed.
Error message
shouldbe
displayedfor
invalidFirst
Name.
7.3.8
(Bug
8147 and
10475)
Creatingnewuser
account…Admin
First Name = valid
Last Name = valid
Email = valid
User ID = valid
Password= valid
Confirm pwd= valid
chars
User successfully created. User successfully
created.
P Correct Input

of 27
3 18.2.1 The Admin functional -testing table
Test Case Description Predictions Result
T-1-01 Admin Login 1. Fill in username and
password 2. The
system validates
whether user account is
valid.
Pass
T-1-02 Adding User 1. Click “Add” button
2. Fill in required data
Pass
T-1-03 Modifying User 1. Click “Modify”
button 2. Modify
category data
Pass
T-1-05 Adding Pictures/Files 1. Click “Add” button
2. Fill in all data
needed
Pass
T-1-06 Delete-User 1. Click “Delete-View”
button
2. data Delete-User,
Pass
T-1-10 Adding 1. Click “Add” button
2. Fill in related data in
fields.
Pass
T-1-11 View User details 1. Click “View” button
2. View patients
details.
Pass
4 18.2.2 The customer application-testing
T-2-01 Register 1. Click “Register”
button 2. Fill in
required data
Pass

of 27
T-2-02 Login 1. Click “Login”
button 2. Fill in data
needed
Pass
T-2-03 View Your Location
On Map
Click Locate ME To
View YourLocation
Pass
T-2-04 Add Emergency
Contact Detail
Click “Add Trusted
Contacts” button 2. Fill
in data needed
Pass
T-2-06 Emergency SOS Click SOS Button Or
Press Power Button
For 3 times.
Pass
T-2-07 Locate Your Friends You Can View Your
Friends/Contacts Live
On Map
Pass
T-2-08 Edit Your Profile 1.Click Edit Button.
2.Change Details.
Pass
T-2-09 Delete Your Profile Click.Del.Profile
Button.
Enter our Password To
Delete Profile
Pass
T-2-10 Logout Click Logout Button Pass
T-2-11 Chat With Friends Click Chat Button.
Select Contact To Chat
With.
Pass
T-2-n ----------------------- ------------------------- -------------------------
The Security Personal application-testing
T-3-01 Register Only Admin Can Add
Security Personals.
Pass

of 27
T-3-02 Login 1. Click “Login”
button 2. Fill in data
needed
Pass
T-3-03 View Your Location Click Locate ME Pass
T-3-04 View Notification Click Notification Tab Pass
T-3-06 View Assigned Jobs. If Someone In Trouble
and Admin assigned You
Job. Targeted Person
Detail Will Shown In
Notification.
Pass
T-3-07 Check Can Make Call
And Chat
Navigate To
ChatRoom
Pass
5 18.3 System Testing
System testing of the software and hardware is a testing conducted on a system which is
complete, integrated system that works as a whole. System testing is a critical testing procedure
that must be conducted by software developer before the system released. During system testing
it can evaluate the system’s compliance with its specified requirements according to the system
design. Furthermore, several testing activities in system testing test not only the design of the
system, but also the behavior and the believed expectations result from the customer. In addition,
various complex test cases that used to test the system are according to the business process
requirements which are collected from the user. Meanwhile, errors or bugs that detected during
the testing is required software developer look into it from the initial step of the business process
to the end of the process to ensure it have expected result in order to solve the errors or bugs to
determine the degree of system stability.
6 18.4 Acceptance Testing
Acceptance testing also known as user acceptance testing would be the final testing procedure
that performs to test the developed software system. In acceptance testing, the testing activities
are different compare to the testing activities that mentioned previously because the tester that
tests the system will be the final user which do not have knowledge about the system logic. If the
final user encountered an error while using the system, system developer are required to maintain
the system as soon as possible and release a new patch for the existing system to recover the
error. Meanwhile, final user will use the system that visualized as to support their realbusiness

of 27
routine operation, therefore software support team are required to stand by to provide technical
support while final user need any help or support that regarding the system. If there is no errors
detected by the final user while using the system for a long period, the development job of
developer is consider as complete and the system will be a final system product.
 Risk Analysis & Management
IMPLEMENTATION RISK
Implementation risk is defined as a combination of risks that may inhibit successfuldevelopment
and deployment of the software. The higher the risk level, the greater the chance of project failure
unless the identified risk factors are mitigated. Implementation risk is estimated by selecting the
most appropriate attributes for each risk factors.
BUSINESS RISKS
Failure to complete the development of Wome Security App will result in continued
excess expenditures by management to support upgrades of systems that are not scalable
and which do not provide adequate interfaces with other applications. Lack of adequate
interfaces will result in continued expenditures of time and effort by staff to duplicate or
replicate data outside of the existing system.
Implementation Risk Factors
Possibility Risk Preventive action
High Problems with system
integration
Well defined interfaces between components and
constant communication between members who are
developing connected components.
High Lack of time to finish
deliverables on time
OR
Under-estimation of required
time and resources.
Setup milestones in advance of the final due date
for each deliverable.
Planning in advance,dividing work equally
between team members to avoid overloading some
team members.
High Requirements change Client will be made aware,in advance, of the
amount of change that can be accommodated within
the term of the project.

of 27
Medium The need for licensed tools
(because of using
commercial platforms and
technologies)
Planning the project from start, elaborating
requirements. Deciding on the tools at the
beginning of the project and making sure all needed
licenses are available.
Medium Inappropriate version of the
tools and components.
Select specific versions of tools and components to
use and every member will adhere to the choice
throughout the entire project.
Medium Unavailability or lack of
resources
Reassign resources to fill the gap, depending on
availability and previous knowledge of what the
currently unavailable resource was working on.
Medium Bad communication between
team members
Regular weekly meetings, PL and TL coordinating
the team.
Medium Lack of motivation for
working on a project
Constant communication between team members
and solving problems together.
Low Lack of knowledge in
technologies
Choosing technologies that most team members are
familiar with, and dividing the work to team
members considering their knowledge.
Low Accidental loss of valuable
information
Making regular backups
Low Team member leaves the
project
Making sure that PL and TL are always informed
about project status. Making sure that always at
least two team members work together on important
parts of the project.
Medium Final product doesn’t meet
the requirements
Regular contact with project supervisor, daily
supervising of work of every team member
Based on the attributes selected for each project risk factor, this project is
estimated to be a Medium risk development effort.
Execution and Monitoring
Project monitoring will adhere to the provisions of the SRS. Project monitoring will be done in all weekly
meetings and approved by the Project Manager. The major monitoring mechanism is the testing phase of
the project. Suggestions with regard to documents can be made by individual team members, senior
management, and/or the customer and shall be approved by the Project Manager.
The executable software will be prepared for each user site, including any batch files, command files, data
files, or other software files needed to install and operate the software on its target computer(s). The result

of 27
is included in the executable deliverable portion of the Program Package (PP) as documented in the Build
Plan
SOFTWARE CONFIGURATION MANAGEMENT:
Software Configuration Management will be performed under the direction of the SCM Manager
according to the processes and procedures defined in the WOMAN SAFTYAPPLICATION, Project
Software Configuration Management Plan. The SCM Manager Verify that configuration identification
of documents, code, and computer data has established standards for titling, naming, and describing
change status.
Verify for document control that only approved, up-to-date documentation is provided for use by
project personnel, and that the document distribution process results in receipt of correct
documentation.
Project communication management:
Approximately 70% of a Project Manager’s time is spent on communication. Project Management Team
are spending most of time on measuring and reporting on the performance of the project, composing and
reading emails, conducting meetings, writing the project plan, meeting with team members, overseeing
work being performed, meeting with partners and many more activities related to the project. By having a
solid communications management approach many project management problems can be avoided. In the
WOMAN SAFTY APPLICATION project the cooperative and open communication approach will be
used This approach will direct the activities throughout the project and it will also create a sustainable
project for the future. WOMAN SAFTY APPLICATION project partners will be encouraged to present
their insights and lessons learned to be available to as broad higher education population at their institution
as possible. We will use multiple communication channels to exchange ideas,information, and reports. We
will use electronic media such as emails, Skype conversations, videoconferences, in order to provide
synchronous conversations while keeping expenses as low as possible. The Project Manager will take a
proactive role in ensuring effective communications on this project. As with most project plans, updates
or changes may be required as the project progresses or changes are approved. Changes or updates may be
required due to changesin personnel, scope,budget, or other reasons.Additionally, updates may be required
as the project matures and additional information is available. The project management team is responsible
for managing all proposed and approved changes to the communications management plan.
Stakeholder Analysis For Project Communication:

of 27
Stakeholders Document Name Document
Format
Contact Person Due
Customer
management
Monthly status
report
Hard copy Abu Bakr First of month
Customer business
staff
Monthly status
report
Hard copy M.Hanan First of month
Customer
technical staff
Monthly status
report
E-mail Zeeshan Ahmed First of month
Internal
management
Monthly status
report
Internal business
and technical staff
Monthly status
report
E-mail Abu Bakr First of month
Training
subcontractor
Training report Hard copy Zeeshan Ahmed 20/7/2020
Software
subcontractor
Software
implementation
plan
Hard copy Abu Bakr 30/7/2020
Software Quality Assurance
The Project Manager requests periodic independent assessments of project SQA. These assessments will
be conducted at least annually. The auditor, who must be independent of the assessed SQA group, will
review SQA audits conducted on the project, including documented findings and corrective actions, and
will consult with project personnel to ensure that SQA activities have been accomplished, and that
corrective actions have been implemented or resolved. The auditor will report findings of the independent
assessment to the Project and, where appropriate, Program Manager.
Execution and Monitoring
Project monitoring will adhere to the provisions of the SRS. Project monitoring will be done in all weekly
meetings and approved by the Project Manager. The major monitoring mechanism is the testing phase of
the project. Suggestions with regard to documents can be made by individual team members, senior
management, and/or the customer and shall be approved by the Project Manager.
The executable software will be prepared for each user site, including any batch files, command files, data
files, or other software files needed to install and operate the software on its target computer(s). The result
is included in the executable deliverable portion of the Program Package (PP) as documented in the Build
Plan
SOFTWARE CONFIGURATION MANAGEMENT:
Software Configuration Management will be performed under the direction of the SCM Manager
according to the processes and procedures defined in the WOMAN SAFTYAPPLICATION, Project

of 27
Software Configuration Management Plan. The SCM Manager Verify that configuration identification
of documents, code, and computer data has established standards for titling, naming, and describing
change status.
Verify for document control that only approved, up-to-date documentation is provided for use by
project personnel, and that the document distribution process results in receipt of correct
documentation.
Project communication management:
Approximately 70% of a Project Manager’s time is spent on communication. Project Management Team
are spending most of time on measuring and reporting on the performance of the project, composing and
reading emails, conducting meetings, writing the project plan, meeting with team members, overseeing
work being performed, meeting with partners and many more activities related to the project. By having a
solid communications management approach many project management problems can be avoided. In the
WOMAN SAFTY APPLICATION project the cooperative and open communication approach will be
used This approach will direct the activities throughout the project and it will also create a sustainable
project for the future. WOMAN SAFTY APPLICATION project partners will be encouraged to present
their insights and lessons learned to be available to as broad higher education population at their institution
as possible. We will use multiple communication channels to exchange ideas,information, and reports. We
will use electronic media such as emails, Skype conversations, videoconferences, in order to provide
synchronous conversations while keeping expenses as low as possible. The Project Manager will take a
proactive role in ensuring effective communications on this project. As with most project plans, updates
or changes may be required as the project progresses or changes are approved. Changes or updates may be
required due to changesin personnel, scope,budget, or other reasons.Additionally, updates may be required
as the project matures and additional information is available. The project management team is responsible
for managing all proposed and approved changes to the communications management plan.
Stakeholder Analysis For Project Communication:
Stakeholders Document Name Document
Format
Contact Person Due
Customer
management
Monthly status
report
Hard copy Abu Bakr First of month
Customer business
staff
Monthly status
report
Customer
technical staff
Monthly status
report
E-mail Zeeshan Ahmed First of month
Internal
management
Monthly status
report

of 27
Internal business
and technical staff
Monthly status
report
E-mail Abu Bakr First of month
Training
subcontractor
Training report Hard copy Zeeshan Ahmed 20/7/2020
Software
subcontractor
Software
implementation
plan
Hard copy Abu Bakr 30/7/2020
Software Quality Assurance
The Project Manager requests periodic independent assessments of project SQA. These assessments will
be conducted at least annually. The auditor, who must be independent of the assessed SQA group, will
review SQA audits conducted on the project, including documented findings and corrective actions, and
will consult with project personnel to ensure that SQA activities have been accomplished, and that
corrective actions have been implemented or resolved. The auditor will report findings of the independent
assessment to the Project and, where appropriate, Program Manager.
Process Model Justification:
The incremental build model is a method of software development where the product is designed,
implemented and tested incrementally (a little more is added each time) until the product is
finished. It involves both development and maintenance. It’s a process of software development
where requirements are broken down into multiple standalone modules of software development
cycle. Each iteration passes through the requirements, design, coding and testing phases.
Incremental model is one of the best software process models for smaller projects. The main
objective of iterative development is to build the system incrementally, starting from basic partial
system features and gradually adding more features until the entire system is completed.
Compared to waterfall, iterative development allows flexibility in accommodating new
requirements or changes thereof. It also provides room for improvement in succeeding iterations
based on lessons learned from previous iterations. And as compared to other process models it is
best for the building the project on that we are working on.
1. Incrementalmodel is one of the best models for smaller project.
2. Generates working software quickly and early during the software life cycle.
More flexible – less costly to change scope and requirements.
3. Easier to test and debug during a smaller iteration.

of 27
Figure 37: Process Model
The End

Mobile/Web App Development Project Report

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Mobile/Web App Development Project Report

Similar to Mobile/Web App Development Project Report (20)

More from Abubakr Cheema

More from Abubakr Cheema (8)

Recently uploaded

Recently uploaded (20)

Mobile/Web App Development Project Report