Академический Документы
Профессиональный Документы
Культура Документы
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:-
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.
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.
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)
MySouq
1.0
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.
Description of Task: Development and documentation of the project budget based on plan and resources.
Description of Task: Identify develop and make documentation of the each stage of project.
1.2) Mockup
Description of Task: Describe the whole system how it work under what constraint etc.
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.
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.
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.
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.
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:
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.
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.
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.
WBS #: 1.4.3
Task: Traceability and impact analysis
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: Set the automatic relationship across requirements, perform real-time impact analysis and
run test cases.
Input: Detail document of specified requirement.
Description of Task: Integrate and checks that the specified requirement support the development technologies.
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.
Description of Task: Identifying the subsystems and making their relationship with system are identified.
WBS #: 1.5.3
Task: Interface design.
Est. Level Effort: 24 hrs. Owner: Software Quality Assurance Team.
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.
Description of Task: Services are allocated to the component and the interfaces for this component is designed.
WBS #: 1.5.5
Task: Data Structure design.
Est. Level Effort: 24 hrs. Owner: System Analyst.
Resources Needed: System analyst, developer. Work Product: System design document.
Description of Task: . The data structure used in this system are designed in detail.
Description of Task: . The algorithm used in this system are designed in detail.
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.
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.
Input: Software Requirement Specification document.
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.
Input: Software Requirement Specification document.
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.
Input: Software Requirement Specification document.
WBS #: 1.7.1
Task: Home Page
Est. Level Effort: 144 hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
Description of Task: Coding the second software increment module task such home Page and its performing their testing
and confirm their quality assurance.
Description of Task: Coding the second software increment module task such Product Categories, Product listing and
performing their testing and confirm their quality assurance.
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.
WBS #: 1.8.1
Task: Vendor Dashboard
Est. Level Effort: 144 hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
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.
WBS #: 1.9.1
Task: Admin Dashboard
Est. Level Effort: 144 hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
Description of Task: Coding the admin side dashboard, they can manage their inventory and keep the record of their
inventory system and much more.
Input: Software Requirement Specification document and client review.
WBS #: 1.10.1
Task: User Account Setting
Est. Level Effort: 16hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
Description of Task: Coding and implementing the user account security features, handling account setting.
Description of Task: Coding and implementing the admin account security features, handling account setting.
Description of Task: Coding and implementing the Vendor account security features, handling account setting.
WBS #: 1.11.1
Task: Payment checkout
Est. Level Effort: 48 hrs. Owner: Developer
Resources Needed: Developer, Software tester Work Product: MS VS Code
Requirement engineer.
Description of Task: Coding and testing the payment checkout method for online ordering of product.
Description of Task: Integrate all module and adding the checkout method, order placing, deleting, updating etc.
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.
Description of Task: Integrate the component of system and test that they work properly together and give the desire
result.
Description of Task: Test the whole component of software system against their specified out comes.
Description of Task: Test the whole system and confirms that specified requirement are fulfilled.
WBS #: 1.12.5
Task: Acceptance Testing
Est. Level Effort: 8 hrs. Owner: Tester
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
- Compatibility Issue
- Test case failing
- UI not well design
- Security
- Robustness
WBS #: 1.13.1
Task: Motivate the end user to use the system
Est. Level Effort: 4 hrs. Owner: Project Manager
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.
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.
Input: All SRS, UI, UX documentation.
WBS #: 1.13.3
Task: Introduce the system to the end-user.
Est. Level Effort: 8 hrs. Owner: Project Manager
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.
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.
WBS #: 1.14.2
Task: Installation Preparations.
Est. Level Effort: 4 hrs. Owner: Project Owner.
Resources Needed: Developer Work Product: MySouq.
Description of Task: Importing the initial customer data, configuring the product, integrating the product, scheduling the
deployment date and creating the deployment package.
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.
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
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.
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
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
Bank
Legal Consultants
Risk Register:
# Probabilit
Risk Trigger/Cause Impact Risk Owner
y
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.
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.
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
components have
Poor architecture design and poor valid
security Quality product may not met. 6-7 Developer
security features.
20 vulnerabilities
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
components aren't Poor architecture design and adopt the Poor quality products, components have
7-8 developer
reliable invalid development model. security vulnerabilities.
24
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
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
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
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 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
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
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.
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.