SPM Completed

MY-SOUQ.
COM
An Ecommerce Website and Mobile Application
22-12-210
3309-FBAS/BSSE/F16
3372-FBAS/BSSE/F16
3365-FBAS/BSSE/F16
3227-FBAS/BSSE/F16
1: Project Scope:-
1.1: Product scope description:-

MySouq is all about multi-vendor ecommerce site. In this system vendors can register and then upload their products. It is easy for
vendors to upload their products without building their own site. It is also cost effective for vendors. The problem was that every vendors
cannot developed their own site to upload their products and also customer in problem because he/she visits all vendors shop to buy
what they want. It is time taken process. But now through this website the problems of customers and vendors are solved. Vendor only
need to register and upload their products and customer only need to search for the required product and then can order that product
through this system. Customer can see the feedbacks for the quality of the product.
MySouq will provide a secure, managed, cloud-based virtual mobile and web experience to end-users. Unlike traditional on-premises
Virtual Desktop Infrastructure (VDI) solutions, end-user doesn’t have to worry about procuring, deploying, and managing a complex
environment –MySouq takes care of the heavy lifting and provides a fully managed service. With MySouq Workspaces, end-user can
deliver a high quality portable desktop, and applications, to your users on the device of their choice.
Whether you are managing traditional desktops or an on-premises solution for Virtual Desktop Infrastructure (VDI), both of these
approaches require significant capital investment and are often difficult to deploy and manage. Using a cloud-based virtual desktop
environment eliminates the need for up-front investment and ongoing management of infrastructure, providing you with an easy, cost-
effective way to bring a secure and broadly accessible desktop experience to your users.
We will start from website the domain name will be MySouq and server will be VPS as per requirements. The system is distributed
system to achieve the high efficiency, and easy maintenance etc. The database of system should be centralized and secure as it will
interact with both the website and mobile apps. The functionality of the site and mobile apps will be the same. Let me list the main
functionality of project.
1:- Registration for vendors and customers.
2:- Dashboard for vendor.
3:- Upload products and its details.
4:- Bulk upload.
5:- Add to cart.
6:- Product listing
7:- Product Categories
8:- Online Payment

9:- Persistent Storage
10:- Order Placing etc.
1.2: Deliverables:-
The Duration of this project is in 8 month. The website will completed in first 5 months and then the last 3 month the
mobile app will be completed.
# Deliverable Name Description Month-Day Status
1 Prepare Project Plan Identify the milestone, timelines of the project and December In Progress
budget.
2 Mockup Basically provide the system simulation or sketch January Not

story of system using and it’s an overview of complete
process.
3 Requirement Elicitation Elicit the requirement by Conducting interview, February Not

analyzing the legacy system, workshop, complete
brainstorming and floating questionnaire et
4 Designing & Writing use-cases ,test cases, architectural diagram February Not
Documentation complete
Domain modeling, system sequence diagram etc.
5 Requirement Definition Defining the requirement in detail and build the February Not
(Functional & short stories according to the requirement, also complete
nonfunctional) choosing the non-functional requirement which is
important for system.
6 Software Development Login, Signup, Service and Contact Pages Module May Not
(Increment-01) complete
7 Software Development Home Page, Product Categories, Product listing, May Not
product adding to cart, Payment method complete
(Increment-02)
8 Software Development Designing and developing the vendor dashboard. June Not
complete
(Increment-03)
9 Software Development Designing and developing the admin dashboard June Not
and also testing of build component. complete
(Increment-04)
10 Software Development User, Vendor and Admin Account setting etc. July Not
complete
(Increment-05)
11 Software Development Payment, Order placing and it related functionalities July Not
performing. complete
(Increment-06)
12 System Testing Performing the integration testing, component August Not

testing, stress testing, load testing, and acceptance complete
testing.
13 Employee training , Motivate, Improve the technical skills and Not

Security awareness elaborating the system. complete
14 Deployment Hosting the whole system at server. August Not

complete
1.3: Acceptance criteria:-
The website should be responsive. All the functionality must working as the requirements. Complete website should be tested through
web load and test complete software. All required non-functional requirements should be tested in proper way and must be documented.
The GUI of the web should be user-friendly. And the most important thing the upload function should be easy to use because not every
vendor can use the system if it is not easy. Once the client is accepted the web then move on the apps. All the functionality of web and
apps should be same. All products should showing in apps also if it is upload from site or mobile apps both types of uploading should
be showing in apps. QA team should test the apps and every test cases should be documented and given to project owner and developers
team. Once the project is tested and meets the requirements then this project is accepted.
1.4: Project Exclusions:-

There are some functionality and some platform which are excluded in project because they may take long-time and it is a lengthy
process.
i) Encryption of user and vendors uploaded data.

ii) The second thing is not included that is telecom services because they also charge per month to provide services and it is a
time taken process. Telecom services means operator send a message to customer and vendor through their sim number or mobile
number.
iii) Third thing which is not included in the project is the iphone app which should not uploaded to app store because they do
not accept the app easily and take a lot of time to test the app and they may call you for introduction of the app and what it will
do and why you uploading it here and so on.
iv) System well not require specific software product to be installed on local systems.
v) System will not implement the all non-functional requirement, because some of non-functionalities are contradict to each
other.
vi) Virtual Desktop Infrastructure (VDI) solutions.
2: Work Breakdown Structure (WBS):
MySouq
1.0
1.9 1.10 1.11 1.12 1.13 1.14

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8
Software Software Software Software Security
Requirem Design & Software Software Software Deploym
Prepare Requirement Developm Develop Developm Develop &
Mockup ent Documentati Development Developme Testing ent
Project Plan Definition ent- 03 ment- 04 ent- 05 ment- 06 Training
Elicitation on - 01 nt- 02
1.7
Admin Compone Motivate

Create Plan Define Anticipatio Detail Architecture Vendor Payment/ Stakehol
Sing Up Home Account nt Testing the End
Process n Description Dashboard Admin Checkout der
Page Setting user
Dashboard Commun
Make budget Investigati Abstract ication
Integratio
Sketch
on Specification
Sign In
Visualization Product n Testing
Vendor Order Improve
Identifying Categories
Account Handling the Installati
Milestone Specificat
Wirefr Interface setting Technical on
ion
Traceability & Design Service Stress Skills Preparati
Project ame
Impact Product Testing on
Charter Analysis of Analysis Listing
Factual
Data Component User Loading
Design Account Test
Integration Contact Introducin
Setting Installation
with Adding g the
different Payment Acceptance System
Data
tools Method Testing
Structure
Design
Algorithm
Design
1.1) Prepare the project plan:
WBS #: 1.1.1 Create plan
Task:
Est. Level Effort: 56 hrs. Owner: Project Manager
Resources Needed: Subject Matter Experts Work Product: MS Project Plan
Description of Task: Development of a detailed project plan that lists all key resources, tasks, milestones, dependencies, and
durations.
Input: Approved Project Charter.

Dependencies: Approval of Budget.
Risk: Changes to IT Apps plans and deliverables.
WBS #: 1.1.2 Make Budget

Task:
Resources Needed: Sponsor, Direct investment Work Product:
Description of Task: Development and documentation of the project budget based on plan and resources.

Risk: -Changes to IT Apps plans and deliverables.
-Remo
WBS #: 1.1.3 Identify the milestone

Task:
Resources Needed: Expert Judgement, Technical and Work Product:
experience employee judgement.
Description of Task: Identify develop and make documentation of the each stage of project.

Risk: - Change in application design.
-Changes Application requirement, plan and deliverables.
WBS #: 1.1.4 Prepare the project charter
Task:
Resources Needed: Operational and general manager Work Product:
are required.
Description of Task: A written description of the project’s product, service, or result and a business Case Reason for undertaking the
project, solution to resolve problems, and analysis of the benefit of cost.
Input: Business documents, Agreement, Enterprise Environment Factor etc.

Dependencies: Some constrain, critical path, and lead and lag etc.
Risk: Changing in requirement etc.
1.2) Mockup
WBS #: 1.2.1 Define processes

Task:
Est. Level Effort: 8 hrs. Owner: UX designer
Resources Needed: One or two team member of Work Product: Balsamiq
requirement engineer team.
Description of Task: Describe the whole system how it work under what constraint etc.
Input: Design document.

Risk: -Changes to design document and requirement document (SRS).
WBS #: 1.2.2 Sketch
Task:
Est. Level Effort: 5 hrs. Owner: UX designer
Resources Needed: One or two team member of Work Product: Balsamiq
requirement engineer team.
Description of Task: It is basically just a raw freehand drawing on a piece of paper that gives you a low-fidelity representation of
app. It is the fastest way to get your idea ready for brainstorming.
Input: Domain Model document.

Dependencies: Design document.
Risk: -Changes to design document and requirement document (SRS).
WBS #: 1.2.3 wireframe

Task:
Est. Level Effort: 3 hrs. Owner: UI designer
Resources Needed: UX designer is required. Work Product: Balsamiq
Description of Task: Describe the functionality of a product as well as relations between views (what will happen when you click a
certain button.
Input: Sketches.
Dependencies: Design document.

Risk: - Changes to sketch
- Changes to design document and requirement document (SRS).
1.3) Requirement Elicitation
WBS #: 1.3.1
Task: Requirements Anticipation.
Est. Level Effort: 7 hrs. Owner: Requirement Engineer

Resources Needed: Requirement engineer require. Work Product: RequisitePro.
Description of Task: Involves to foresee the likelihood of certain problems or features and requirements for a new system. As a
result, the features they investigate for the current system, questions they raise, or methods employed may be
based on this familiarity
Input: Features which are on demand.
Dependencies: Development technology which is preferred by client

Risk: - Changes to feature
WBS #: 1.3.2
Task: Requirements Investigation.

Description of Task: Study the current system and document its features for further analysis. Requirements investigation relies on
the fact-finding techniques and includes methods for documenting and describing system features.
Input: Features which are on demand.

Risk: - Changes to feature
WBS #: 1.3.3
Task: Requirements Specification.

Description of Task: The data produced during the fact-finding investigation are analyzed to determine requirements
specifications, the description of features for a new system. This activity has three interrelated parts:
Input: Requirement which is specified at high level

Risk: - Requirement Conflict.
WBS #: 1.3.4
Task: Analysis of Factual Data.
Est. Level Effort: 5 hrs. Owner: Requirement Engineer.

Resources Needed: Requirement engineer require and Work Product: FineReport.
some judgments of data analyst.
Description of Task: The data collected during the fact – finding study and included in data flow and decision analysis
documentation are examined to determine how well the system is performing and whether it will meet the
organization’s demands
Input: Client requirement at high level.

1.4) Requirement Definition:

WBS #: 1.4.1
Task: Detail Description of Requirement

Resources Needed: Requirement manager and Work Product: ReQtest.
requirement engineer.
Description of Task: This includes the ability to define requirements, model relationships between them, reuse requirements, and
export/import requirements data for creating requirements documentation.
Input: All specified requirement.

WBS #: 1.4.2
Task: Requirement visualization.
Resources Needed: Requirement engineer. Work Product: ReQtest.
Description of Task: This includes show the interactive flows and simulation, choosing the requirement which is possible to make
the storyboard and show the functionality in graphic model.
Input: All specified requirement.

Risk: - Client insist to fulfil the specified requirement.
WBS #: 1.4.3
Task: Traceability and impact analysis
some judgments of data analyst.
Description of Task: Set the automatic relationship across requirements, perform real-time impact analysis and
run test cases.
Input: Detail document of specified requirement.
Dependencies: Detail document of specified requirement.

Risk: - Security issues, system degrade.
WBS #: 1.4.4
Task: Integration with different tools.
developer.
Description of Task: Integrate and checks that the specified requirement support the development technologies.
Input: Detail document of specified requirement.
Dependencies: Development technologies.

Risk: - System degrade and may system down.
1.5) Design Process
WBS #: 1.5.1
Task: Architecture design.
Est. Level Effort: 32 hrs. Owner: Software Quality Assurance Team.
Resources Needed: System analyst and developer. Work Product: System design document.
Description of Task: Identifying the subsystems and making their relationship with system are identified.
Input: SRS document, software development model etc.
Dependencies: SRS document.

Risk: - Identifying those sub systems which are not compatible.
WBS #: 1.5.2
Task: Abstract specification.
Est. Level Effort: 32 hrs. Owner: System Analyst.
Resources Needed: System analyst and developer. Work Product: System design document.
Description of Task: Identifying the subsystems and making their relationship with system are identified.
Input: SRS document, software development model etc.
Dependencies: SRS document.

Risk: - Identifying those sub systems which are not compatible.
WBS #: 1.5.3
Task: Interface design.
Resources Needed: System analyst, UI and UX designer. Work Product: System design document.
Description of Task: For each sub system, its interface with others is designed.
Input: UX design document.
Dependencies: UI design document.

Risk: - Delays in completion.-Claims for damages.-Stakeholder complaints. Reputational damage.
WBS #: 1.5.4
Task: Component design.
Resources Needed: System analyst, developer. Work Product: System design document.
Description of Task: Services are allocated to the component and the interfaces for this component is designed.
Input: Design document.

Dependencies: UI design document.
Risk: i) Evaluation ii) Integration. Iii) Context iv) Quality v) Process
WBS #: 1.5.5
Task: Data Structure design.
Description of Task: . The data structure used in this system are designed in detail.
Input: SRS document.

Dependencies: Component design document.
Risk: i) Integration. ii) security iii) Process
WBS #: 1.5.6
Task: Algorithm design.
Description of Task: . The algorithm used in this system are designed in detail.
Input: Data structure document.

Dependencies: Data structure document.
Risk: i) Efficiency ii) security
1.6) Software development (Increment 01):
WBS #: 1.6.1
Task: Sing UP
Est. Level Effort: 24 hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
Description of Task: Developing/Coding the first software increment module such user, admin, super admin signup,
and also performing its testing and confirm its quality assurance.
Input: Software Requirement Specification document.
Dependencies: - Testing Plans and test cases.

Risk: - Defects
- Compatibility Issue
- Test case failing
- UI not well design
- Security
- Robustness
WBS #: 1.6.2
Task: Sing In
Description of Task: Developing/Coding the first software increment module tack such user, admin, and super admin
also performing its testing and confirm its quality assurance.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.6.3
Task: Service
Description of Task: Developing/Coding the first software increment module task such organization and company
services pages and its related functionalities also performing it’s testing and confirm its quality
assurance.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.6.4
Task: Contact Page
Description of Task: Developing/Coding the first software increment module such user, admin, super admin contacts,
and also performing its testing and confirm its quality assurance.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.7.1
Task: Home Page
Description of Task: Coding the second software increment module task such home Page and its performing their testing
and confirm their quality assurance.
Input: Software Requirement Specification document and client review.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.7.2
Task: Product Listing and Categories
Description of Task: Coding the second software increment module task such Product Categories, Product listing and
performing their testing and confirm their quality assurance.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.7.3
Task: Implementing the Cart Process
Description of Task: Coding the second software increment module task such Product adding to cart, updating the cart
product etc. and performing their testing and confirm their quality assurance.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.8.1
Task: Vendor Dashboard
Description of Task: Coding the vendor side dashboard, by which they can manage their inventory and keep the record
of their inventory system and much more.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.9.1
Task: Admin Dashboard
Description of Task: Coding the admin side dashboard, they can manage their inventory and keep the record of their
inventory system and much more.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.10.1
Task: User Account Setting
Est. Level Effort: 16hrs. Owner: Developer
Description of Task: Coding and implementing the user account security features, handling account setting.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.10.2
Task: Admin Account Setting
Description of Task: Coding and implementing the admin account security features, handling account setting.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.10.3
Task: Vendor Account Setting
Description of Task: Coding and implementing the Vendor account security features, handling account setting.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.11.1
Task: Payment checkout
Description of Task: Coding and testing the payment checkout method for online ordering of product.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.11.2
Task: Order manging/placing
Description of Task: Integrate all module and adding the checkout method, order placing, deleting, updating etc.
Dependencies: -Testing Plans and test cases.

- All previous requirement those implemented successfully.
Risk: - Defects
- Test case failing
- Security
- Robustness
1.12) System Testing
WBS #: 1.12.1
Task: Unit Testing
Est. Level Effort: 16 hrs. Owner: Tester
Resources Needed: Software tester. Work Product: Junit, NUnit
Description of Task: Test all individual functions against their specified out comes.
Input: Functions of module which are coded.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.12.2
Task: Component Testing
Resources Needed: Software tester. Work Product: Junit, NUnit
Description of Task: Integrate the component of system and test that they work properly together and give the desire
result.
Input: All module of system.
Dependencies: -Testing Plans and test cases and system module.

Risk: - System degrade.
- Defects
- Test case failing
- Security
- Robustness
WBS #: 1.12.3
Task: Integration Testing
Resources Needed: Software tester and one quality Work Product: Junit, NUnit
assurance team member.
Description of Task: Test the whole component of software system against their specified out comes.
Input: All unit of that component.

Risk: - Defects
- Test case failing
- Security
- Robustness
WBS #: 1.12.4
Task: System Testing
Resources Needed: Software tester and one quality Work Product: Junit, NUnit
assurance team member.
Description of Task: Test the whole system and confirms that specified requirement are fulfilled.
Input: All module of system.
Dependencies: -Testing Plans and test cases and system module.

Risk: - Whole system may fail or may some component not work properly.
- System degrade.
- Defects
- Test case failing
- Security
- Robustness
WBS #: 1.12.5
Task: Acceptance Testing
Resources Needed: Client and end-user. Work Product: Work environment.
Description of Task: Testing done by client and end-user that confirms that system is useful for them and system
which was desirable.
Input: SRS, Whole system , client and end-users.
Dependencies: -Environment where the system will use, environment technology which are already represent , end-user technical skills
etc.
Risk: - End-user which are not familiar with technology.
- Whole system may fail or may some component not work properly.
- System degrade.
- Defects
- Test case failing
- Security
- Robustness
1.13) End-user training:
WBS #: 1.13.1
Task: Motivate the end user to use the system
Resources Needed: Manager and software quality Work Product: Simcad Pro.
assurance team.
Description of Task: A simulation is an approximate imitation of the operation of a process or system. Simulation is used for
Performance tuning or optimizing, safety engineering, testing, training, and educate the end-users.
Input: All SRS, UI, UX documentation.
Dependencies: - end-user technical skills and motivations etc.

Risk: - System may not replicate the working environment processes.
- The overall structure of environment has been changed.
WBS #: 1.13.2
Task: Improve the technical skill of end-users
Resources Needed: Manager and software quality Work Product: Mysouq.
assurance team.
Description of Task: Summarize and elaborate a little bit of technologies which is being used in this software system and tell them
how they work together and what is process to use it etc.

WBS #: 1.13.3
Task: Introduce the system to the end-user.
Resources Needed: Manager and software quality Work Product: MySouq.
assurance team.
Description of Task: Introduce the system, its configuration data, system usage help booklet etc. to end-user and also tell them how
the system will actually help you and optimize your processes using the system.

1.14) Deployment Activities:
WBS #: 1.14.1
Task: Stake holder communication.
Est. Level Effort: 2 hrs. Owner: Project Owner.
Resources Needed: Developer Work Product: MySouq.
Description of Task: Informing the stakeholders of deployment contents, training the users and support the users.
Input: -Technical skills of end-users.
Dependencies: - type of technology which are used to deploy the system.

Risk: - The whole or some part of system not work properly.
WBS #: 1.14.2
Task: Installation Preparations.
Description of Task: Importing the initial customer data, configuring the product, integrating the product, scheduling the
deployment date and creating the deployment package.
Input: -Configuration data of product and also end-user product.
Dependencies: -type of data which is being used to configure the product.

Risk: - The system may have valunarities.
WBS #: 1.14.3
Task: Installation.
Description of Task: Pre-install checks, making rollback possible, installing the product, transferring the product from test to
production environments and maintaining information about deployed products.
Input: -the whole system and its dependencies.
Dependencies: -the hosting server, security features, and configuration data etc.
Risk: - Hosting server may not allowed the stress, load and compatibility issues.
Communication Channels:
Total Stakeholder = n = 41
Number of potential communication channels = n*(n-1)/2
Number of potential communication channels = 41*(41-1)/2
Number of potential communication channels = 41*(40)/2 = 1640/2 = 820

ST A K E H O L D E R R E G I S T E R
Project Title: MySouq.com Date Prepared: <12-12-2019>
Im Infl
pa uen Attitude
Contact
Stakeholder Roles in Responsibility in Department/Su Classifi Main Major ct ce about
ID Title Informati Notes
Name Project Project pervisor cation Expectations Requirement (1 (1 the
on
to to Project
5) 5)
1.
Training and
work
Making major 03355203 Develop and experience, as
corporate decisions 304 communicat well
Tariq Mr CEO and managing the Owner tariq.khan NO e a vision and as important 5 5
overall operations @gmail.co a strategy for skills in areas
and resources of a m the company like schedule
company management
and leadership
2.
Manage
complaint,
03355203 Monitoring
Mange
To manage all 309 and
Vendors,
sohail Mr Admin products and issues CEO sohail.kha NO controlling 2 4
Manage
n@gmail.c
customer
om
3.
Is responsible for 03355201

Hiring the Experience is
recruiting, screening, 102
Aamir Mr HR Management No correct the main 3 3
interviewing and Aamir@g
employee requirement
placing workers mail.com
4.
Have
03355203 Knowledge
khalid Mr Client owner none NO 5 5
333 about what
he want
5. 03355203
Is responsible for Planning, BS in
308
overseeing and leading, management,
Abdullah.
Abdullah Mr Manager leading the work of a Management NO controlling business and 1 1
bsse3300
group of people in and work
@iiu.edu.
many instances organizing experience
pk
6. Project Good in
Abdullah Is responsible to 03355203 BS in
Mr Coordinato Management communicati 1 1
khan assist manager 300 management
r on skills
abdullahk
han@gma
il.com
7.
Is responsible of the
requirement. Clear 03355202 Correct and
Requireme
requirements should Project 200 clear BS in computer
Nasir Mr nt engineer NO 4 4
listed and maximum Management nasir@gm requirements science
(1)
requirement should ail.con is identified
be identify.
8. Is responsible of the
requirement. Clear
03355202 Correct and
Requireme requirements should
Project 201 clear BS in computer
Nadeem Mr nt engineer listed and maximum NO 4 4
Management Nadeem@ requirements science
(2) requirement should
gmail.com is identified
be identify.
9. Required a BS
A proper
Is responsible for degree in
03355203 design of the
database design, computer
310 product
Designer frontend and Research and science in
Majid Mr majid.bsse NO included 3 2
(1) backend design development extra a plus
3309@iiu. diagrams,
according to he point will be if
edu.pk graphs and
requirement have an
tables
experience
10. Required a BS
A proper
Is responsible for degree in
03355203 design of the
database design, computer
311 product
Designer frontend and Research and science in
Owais Mr Owais.bss NO included 3 2
(2) backend design development extra a plus
e3325@ii diagrams,
according to the point will be if
u.edu.pk graphs and
requirement have an
tables
experience
11. Developer 03355203 Frontend BS in computer
Mudassir Mr Development NO 4 2
(1) 320 should be science is
Is responsible to Mudassir. responsive required and
develop the product bsse3365 and design must have a
according the design @iiu.edu. should be frontend skill
and responsible for pk follow and and must have
frontend easy to use a knowledge in
development at least one
frontend
language
12. BS in computer
science is
Frontend
Is responsible to required and
03355203 should be
develop the product must have a
330 responsive
Developer according the design frontend skill
Anas Mr Development Anas.bsse NO and design 4 2
(2) and responsible for and must have
3365@iiu. should be
frontend a knowledge in
edu.pk follow and
development at least one
easy to use
frontend
language
13. System BS in computer
should be in is required and
working must have
condition skills in
Is responsible to
03355203 and database backend
develop the product
340 must be languages like
Developer according the design
Tariq faqira Mr Development tariq.bsse NO implementin node.js also 4 2
(3) and responsible for
3372@iiu. g according have skills in
backend
edu.pk to design. database and
development
Third party third party API
API should experience will
giving the result in plus
correct data point
14. BS in computer
03355203
Is responsible to System is required and
Majid ali Developer 350
Mr develop the product Development NO should be in must have 4 2
khan (4) majidalikh
according the design working skills in
an.bsse33
and responsible for condition backend
frontend 16@iiu.ed and database languages like
development u.pk must be node.js also
implementin have skills in
g according database and
to design. third party API
Third party experience will
API should result in plus
giving the point
correct data
15. System BS in computer

should be in is required and
working must have
condition skills in
Is responsible to
03355203 and database backend
develop the product
360 must be languages like
Developer according the design
Uzair Mr Development uzair.bsse NO implementin node.js also 4 2
(5) and responsible for
3315@iiu. g according have skills in
frontend
edu.pk to design. database and
development
Third party third party API
API should experience will
giving the result in plus
correct data point
16. Have
knowledge in
frontend and
03355203
also have BS in computer
370
Is responsible for QA is also a part skills in science and
Darya khan Mr Tester daryakha NO 2 1
frontend testing of development testing experience is
n@gmail.
software’s also required
com
like web
complete
testing
17. Can test the
Is responsible for QA is also a part 03355203 BS in computer
Asad khan Mr Tester NO system 2 1
backend testing of development 380 science and
through
daryakha testing experience is
n@gmail. software’s also required
com and have
good
knowledge
about QA
and QC
18. Every
It
Is responsible for product is Must have
can
Redtag Vendors their products quality - - NO correctly knowledge of 2 2
be
and price. uploaded in system
both
the system
19. It can Is responsible for
Ahmed be Customers giving details for - - NO - - 1 1
both shipment
20. Is responsible to
Wasel.com org Shipments - - NO - - 2 2
provide shipments
21. Souq.com org Competitor - - - NO - - 2 0
22. Noon.com org Competitor - - - NO - - 2 0
23. Tax
FBR org - - - NO - -
Authority
24. Sheikh
Org Sponser - - - NO - - 1 0
Rasheed
25. Api
Google Org - - - NO - - 1 0
provider
26. Provide
Oracle Org - - - NO - - 1 0
database
27. Investor/Sh 1
Riyad Bank Org areholder/ - - - NO - - 0
Sponsor
28. NCB Org Bank - - - NO - - 1 0
29. Alinma bank Org Bank - - - NO - - 1 0
30. Bank AlJazira Org Bank - - - NO - - 1 0
31. Al Rajhi Bank Org Bank - - - NO - - 1 0
32. Social Media 1
Org - - - - NO - - 0
Team
33. API 1
Google Org - - - NO - - 0
Provider
34. Provide the Provide the
Resource all resource Provide the good quality
Org - - NO - 4
Manager needed for resources resources 4
project. within time.
35. Application 1
Host the
hostinger
Hosting comp To host the application
- @gmail.co NO - 0
Service any application on server on server
m
Provider successfully.
36. Project
gov@pk.c Provide the
Government org legalization - - NO - 5 5
om security etc.
, regulation
37. Elicit the
Mange the Elicit the
Inventory requirement about dummy@
both inventory - NO valid - 5
Manager the inventory from gmail.com 5
system requirement.
vendors
38. Provide the
Confirm the
valid detail dummy@ Tell what 4
Store owner both requirement what - NO - 4
about the gmail.com they want
they want
project
39. Improve the
Provide the
Take the eye on system
good
Technical competitor and new dummy@ feature and 4
both consultanc - NO - 4
Consultant feature what gmail.com meet the
y about the
customers want customer’s
project
requirement.
40. Oversee the
Analyze Developing the
Marketing dummy@ promotion of
both industry marketing strategy - NO - 5
Manager gmail.com the 5
trends and for the company.
company.
demand
products
41. advise
people,
Provide the Provide the
businesses
consultancy at every legal
Legal or dummy@ 3
both new laws, - NO consultancy - 3
Consultants organizatio gmail.com
amendment by and defend
ns with
GOVT. the project.
their legal
obligations
Arrange stakeholders in power/Interest Grid
Keep Satisfied Managed closely
CEO Frontend developer

Admin Backend developer
HR Designer
High Power
Management Database provider

Project coordinate API provider
Requirement engineer Resource Manager
Technical Consultant Shipment provider
Testing Hosting / server
Client
Customer
Monitored Keep Informed

Government
Vendor Store owner
Inventory FBR
Marketing
Competitors
Social Media
Low Power
Bank
Legal Consultants
Risk Register:
# Probabilit
Risk Trigger/Cause Impact Risk Owner
y
-Poor Requirements Analysis.

They require additional resource, time
Project Manager,
1 Scope Creep - Lack of Change Control and cost which were not accounted for at 7-8
Requirement Manager.
the beginning.
-Not Involving Users Early Enough.
-Mapping incorrect expectations

They require additional time and cost for
management for which were not
2
-Using inappropriate communication methods accounted for at the beginning.
Stakeholders have
inaccurate 6-7 Requirement Engineer
expectations
 Rude behavior
 Work-life imbalance.
Stakeholder  The job did not meet expectations. Result in low morale.
3 4-5 Resource Manager
More resource may hire.
turnover  Employee misalignment.
 Feeling undervalued.
More Resource need, time consuming,

Stakeholder
Stakeholder Have different domain and want to solve again prepare the project plan to solve
5-6 Management Team and
4 conflict. their domain problems. different stakeholder problem the
Requirement Engineer.
problem.
Not hiring the resource on time. More Resource need, time consuming,
Resource again prepare the project plan to solve
4-5 HRM
5 shortfalls different stakeholder problem the
Not take the valid compabitable resource.
problem.
Trainer is not well competent.

Technical skills are not grooming well
Training isn't
6 Trainer is not serious. and technical and others not perform 4-5 HRM
available.
well.
Training is Training is often a poor substitute for Delay of project, Quality of product not
3-4 HRM
inadequate professional experience produce.
7
Resources who are just out of school or who
Resources are are new to your industry or profession tend
Poor Quality of Product 4-5 HRM
8 inexperienced to make more mistakes and be less
productive.
Resource Resources who perform below expectations,

Poor Quality of Product 6-7 HRM
performance issues. not valid resource.
9
Cause of valid and useful resource and

Resource turnover Increasing the cost, delay the project. 5-6 HRM
resource may expire.
10
Low team May be low salary, project team not

Delay the project, more Resource hiring 3-4 HRM
motivation corporate to each other’s etc.
11
Architecture fails to
May be cause of to elicit the validate May fail to produce the quality products,
pass governance 5-6 HRM
requirement. Increase the cost of project.
12 processes
Architecture lacks Supporting the strict process to which is Needs to be reworked, cost increasing
4-5 Scope Manager.
flexibility difficult to change. and delay project.
13
Architecture is not fit
Low quality planning. Decrease the quality of products. 6-7 Quality Manager.
for purpose
14
Architecture is Planning is not well designed and Processes are not optimized, which
7-8 Project Manager.
infeasible developed. cause of low quality product.
15
Not valid requirement elicitation, not well Stakeholder requirement conflict each
Design is infeasible. 6-7 Scope Manager.
scope well define. other.
16
Design is not fit for May casue of delay of project and need Software Quality
low quality and design of requirement. 5-6
purpose more resource. Assurance
17
Design fails peer Software Quality

architectural experts review your designs More resource and time consuming 3-4
review Assurance
18
Components aren't Poor design and not valid technologies are

Not meet the requirement within scope. 6-7 Developer
scalable. used.
19
components have
Poor architecture design and poor valid
security Quality product may not met. 6-7 Developer
security features.
20 vulnerabilities
components are Poor quality products, components have

Poor technical developer and tester. 5-6 Developer
over-engineered security vulnerabilities.
21
components lack Poor architecture design and poor valid Vulnerabilities issues come, which also
6-7 Developer
stability security features. cause of low quality products.
22
System may not handle the unique

components aren't Poor architecture design and adopt the
situation which also decrees the quality of 6-7 developer
extensible invalid development model.
23 products.
components aren't Poor architecture design and adopt the Poor quality products, components have
7-8 developer
reliable invalid development model. security vulnerabilities.
24
Information security Not well test cases preparation, and poor

Components have security vulnerabilities. 6-7 Tester
incidents valid security features.
25
Whole system may fail, low quality

System outages Not well secure technologies used. 5-6 Developer Manager
product.
26
Legacy components Reducing vulnerabilities may fail and

SQL team may not well competent. 4-6 SQA Team
lack documentation future updating may also fail.
27
Legacy
Technical Consultant not provide the valid
components are out Project may go out of scope. 3-4 Technical Consultant.
and proper consultancy.
28 of support
components aren't Poor quality products, components have

Not well secure technologies used. 3-6 Developer
maintainable security vulnerabilities.
29
tool problems & May not provide the proper and on time Delay the project and increase the cost of
4-5 HRM
issues resource. products.
30
Failure to integrate Poor quality products, components have

Not compabitable technology used. 6-7 Developer
with systems security vulnerabilities.
31
Delays to required Poor architecture design and adopt the Reducing vulnerabilities may fail and
4-6 Developer
infrastructure invalid development model. future updating may also fail.
32
Failure to integrate Whole system may fail, low quality

Not well secure technologies used. 4-6 Developer
with systems product.
33
Integration testing
Not well test cases preparation, and poor
environments aren't Components have security vulnerabilities. 4-5 Developer
valid security features.
34 available
Project disrupts Software not work properly, low product

Not competent developer are hired. 4-5 Tester
operations quality.
35
Project disrupts Requirement not clear and also domain Project cost increase and project delay
5-7 Tester
sales. modelling not well defined. and required more resource.
36
Project disrupts Gold plating and audit requirement not Project risk may not handle proper which
4-5 Requirement Engineer
compliance understand clearly. is cause of low product.
37
Low quality of interface design and not easy Project cost increase and also need more
Vendors start late 4-5 UI and UX Designer
to use. resource to meet the requirement.
38
Infrastructure is low Project cost increase and also need more

UI and UX is not well defined. 4-5 UI and Tester.
quality resource to meet the requirement.
39
Service quality is . Vendor components are low quality as well Project cost increase and project delay
4-5 Tester and UI
low customer components are low quality. and required more resource.
40
-project spans areas that are compliance-

Legal & regulatory sensitive Stakeholder management fail due to
change impacts 4-5 Legal Consultant
41 illegal activities.
project
-regulatory change as a risk.
Market forces Project cost increase and project delay

Poor marketing strategy and techniques. 4-5 Marketer
impact project and required more resource.
42
Technical change Not well and proper tools and technologies Poor quality products, components have
6-7 Technical Consultant
impacts project are used. security vulnerabilities.
43
Business change Business innovation changes your industry Project cost may increase and utilize
4-5 Marketer Consultant
impacts project and impacts the project. invalid ways.
44
Lack of
Resource constraints cause the project to Risk management may fail due to invalid
management or 7-8 Manager
skip certain project. resource including.
45 control
Failure to follow Not use proper model for development of System not optimize and coherent to
6-7 Developer
methodology software. Processes are not align well. increase the efficiency.
46
Users reject the Not well designed the UI and not easy to Poor and ambiguous UI requirement
7-8 UI and UX
prototype use. elicitation.
47
48
User interface is low Provide the bad user experience and
Slow-loading sites, unnecessary complexity 6-7 UI and UX
quality which also cause of low product quality.
and Lack of engagement.
Time required to upload the data which

User interface isn't More complex data loading and high
cause the more time taking, which impact 5-6 UI and UX
accessible complex color scheme.
49 the quality product.
Strict and froze technologies and

Project reduces Cost increase due to adopting the new
methodologies are used to develop the 7-8 Project Manager
innovation. technologies and methodologies.
50 system.
Key Terms
Risk: The risk stated in a complete sentence which states the cause of the risk, the risk, and the effect that the risk causes to
the project.
Probability: The likelihood that a risk or opportunity will occur (on a scale from 0 to 10 with 10 being the highest).
Impact: The impact of the risk on the project if the risk occurs (scale from 0 to 10 with 10 being the highest)..
Trigger: Something which indicates that a risk is about to occur or has already occurred.
Risk Owner: The person who the project manager assigns to watch for triggers, and manage the risk response if the risk
occurs.

SPM Completed

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SPM Completed

Încărcat de

Drepturi de autor:

Formate disponibile

MY-SOUQ.

1.1: Product scope description:-

2:- Dashboard for vendor.

3:- Upload products and its details.

4:- Bulk upload.

5:- Add to cart.

6:- Product listing

7:- Product Categories

8:- Online Payment

2 Mockup Basically provide the system simulation or sketch January Not

3 Requirement Elicitation Elicit the requirement by Conducting interview, February Not

12 System Testing Performing the integration testing, component August Not

13 Employee training , Motivate, Improve the technical skills and Not

14 Deployment Hosting the whole system at server. August Not

1.4: Project Exclusions:-

i) Encryption of user and vendors uploaded data.

1.9 1.10 1.11 1.12 1.13 1.14

Admin Compone Motivate

Input: Approved Project Charter.

WBS #: 1.1.2 Make Budget

Input: Approved Project Charter.

WBS #: 1.1.3 Identify the milestone

Input: Approved Project Charter.

Input: Business documents, Agreement, Enterprise Environment Factor etc.

WBS #: 1.2.1 Define processes

Input: Design document.

Input: Domain Model document.

WBS #: 1.2.3 wireframe

Dependencies: Design document.

Est. Level Effort: 7 hrs. Owner: Requirement Engineer

Dependencies: Development technology which is preferred by client

Est. Level Effort: 6 hrs. Owner: Requirement Engineer

Input: Features which are on demand.

Dependencies: Development technology which is preferred by client

Est. Level Effort: 6 hrs. Owner: Requirement Engineer

Input: Requirement which is specified at high level

Dependencies: Development technology which is preferred by client

Est. Level Effort: 5 hrs. Owner: Requirement Engineer.

Dependencies: Development technology which is preferred by client

1.4) Requirement Definition:

Est. Level Effort: 5 hrs. Owner: Requirement Engineer.

Input: All specified requirement.

Dependencies: Development technology which is preferred by client

Input: All specified requirement.

Dependencies: Development technology which is preferred by client

Dependencies: Detail document of specified requirement.

Input: Detail document of specified requirement.

Dependencies: Development technologies.

Input: SRS document, software development model etc.

Dependencies: SRS document.

Input: SRS document, software development model etc.

Dependencies: SRS document.

Input: UX design document.

Dependencies: UI design document.

Input: Design document.

Input: SRS document.

Input: Data structure document.

Input: Software Requirement Specification document.

Dependencies: - Testing Plans and test cases.

Dependencies: - Testing Plans and test cases.

Dependencies: - Testing Plans and test cases.

Dependencies: - Testing Plans and test cases.

Input: Software Requirement Specification document and client review.

Dependencies: - Testing Plans and test cases.