ISY3002 - Project Management Plan and SRS Report for Ecommerce

This report presents a Project Management Plan (PMP) and Software Requirements Specification (SRS) for an e-commerce website designed to operate within Australia. The report begins with an introduction to project management plans and software requirements specifications, highlighting their importance in software development. It then details the project management plan, including the project charter, which outlines the project's objectives, stakeholders, and deliverables. A work breakdown structure (WBS) is provided to organize the project's tasks, followed by a risk management plan that identifies potential risks and mitigation strategies. The report also includes software requirements specifications, covering functional and non-functional requirements. The project aims to enhance the firm's sales by expanding its audience through online shopping, integrating with banking systems for secure transactions, and offering various payment options. The report covers critical aspects of project planning, risk assessment, and software specifications, providing a comprehensive overview of the project's structure and requirements. It also includes a work breakdown structure, risk management plan, and software requirements specifications. The report discusses project management, technical design, testing, and training aspects of an e-commerce website.

Report
Table of Contents

Introduction......................................................................................................................................3
Project Management Plan.......................................................................................................3
Project Charter........................................................................................................................3
Work Breakdown Structure....................................................................................................5
Risk Management Plan...........................................................................................................8
Software Requirements Specification..................................................................................10
Conclusion.....................................................................................................................................12
References......................................................................................................................................13

Introduction
Project management plan refers to formal as well as approved document which defines
the ways in which project is being implemented, monitored and controlled. It can be a detailed
summary of planning documents. Software requirement specification refers to explanation of
software system which has to be developed. It is liable for illustrating functional as well as non-
functional requirements (Ali and John, 2020). This report is based on PMP and SRS for
ecommerce website for shopping that delivers their services around Australia. The basic
functions which will be covered by website are selling of products via online medium and all the
processing or transaction can be conducted via this process. This will be aligned with banking
systems so that customers can easily make payments for products which they have purchased and
here different bank options will be provided to them so that they can have feasibility. The
strategic objective is to amplify the overall sales of firm by reaching maximum number of
audiences. This report will cover aspects related with project management plan, project charter
and ways in which tasks or work is done by making use of work breakdown structure.
Furthermore, risk management plan will be discussed for analysing probable threats and at last
software requirement specifications are being provided.
Project Management Plan
The approved and formal document which is liable for illustrating the ways in which projected is
being executed, tracked and managed is referred to as project management plan. Basically, it is
utilised for defining approach that is being taken up by project team delivering intended project
management scope of project (Ferreira and Canedo, 2020). It identify project outcomes, how
successful will be results attained, who will be involved and how this project will be measured as
well as communicated. The crucial aspects related with online shopping website in context of
project management plan are illustrated in next section.
Project Charter
The formal short document which describes project entirely as well as comprises of
objectives, ways in which it will be done and stakeholders is referred to as project charter. This is
crucial aspect while planning out website as this will be utilised within project lifecycle (Herrera
and et. al, 2020). With respect to ecommerce shopping website, the essential aspects are
mentioned below:

Project Title: “Project Management Plan and Software Requirement Specification for
ecommerce shopping website”
Project Sponsor: They will be an owner of firm who are looking forward to have a website
for conducting their operations. Mr. Joe Williamson and Mr. Henry will be sponsors of this
project.
Project Manager & Team members: Mr. Jack Patterson will be project manager as they
have professional experience in this filed and will be liable for planning, procurement as well as
implementation of the project by ensuring that things are done accurately and precisely. There
will be a team of three members who will be responsible for carrying out this project. They are,
John, Peter and Harry.
Objectives: The objective of this project is to furnish a project management plan as well
as software requirement specification for ecommerce website which will be used for shopping.
Basically, these are the documents which comprises of all the details related with the project n
which all the aspects about ecommerce website will be covered to provide sponsors with
adequate knowledge related with project (Kermanshachi and et. al, 2020). This is just a
document and not an execution of project; owner can make alterations if they think any peculiar
aspect should not be there or adding up something. According to final discussion the actual
implementation will be done. Generally, this project aims at giving brief overview of all the
perspectives needed within ecommerce website.
Deliverables: The tangible or intangible services or goods which are produced as an
outcome of project that are intended to be delivered to their customers. With respect to this
project, deliverables comprises of document that comprises of project management plan along
with software requirement specification. Here, it can be considered as an outcome that has to be
attained.
Expected Benefit: From perspectives of project developers team can have adequate
amount for developing documents and if things go well then they will also have an option to
develop website for their client. Along with this a long term relationship will be formed that may
aid them to have more clients (Li, Verhagen and Curran, 2020). On the other hand, firm for
whom this work is done can have significant knowledge about their website and can have
significant increase in sales.
Assumptions/Constraints:

Time Frame: It is necessary to understand all the requirements of firm for whom project
will be developed. Accordingly team has to be developed who are experienced in such kind of
tasks and all the tasks must be elaborated to them. They may have their own innovative ideas to
deal with peculiar project and all will give their point of view, accordingly plan will be
formulated and work will be divided among team (Loehr, Suzuki and Mallick, 2020). Normally
it will take a time of around 5 days as it involves planning, analysis and identification of
probable requirements from both ends that is organisation and what customers expects from
ecommerce websites. It will take 15 days to have a working website.
Budget: For this project in which documents are formulated the cost will be $15,000 but in
case if website for ecommerce shopping has to be developed then the overall budget will be
$30,000.
Work Breakdown Structure
The key project deliverables which organizes team’s work within manageable sections is
referred to as work breakdown structure. It visually illustrates scope within manageable chunks
which can be understood by each project member, each chunk renders further definition as well
as details related with the project (Raharjo and Purwandari, 2020).
Illustration 1: Work Breakdown Structure
The WBS clearly illustrates the way in which work has been divided and it also depicts
sequence in which it will be done. These are illustrated below:

Project Management: Project Charter: It will state the objective, scope and definition of project that will be
carried out. Project Plan: As per the project charter which been identified the plan will be developed
like number of team members, analysing needs of clients, etc. Project Schedule: As project has to be completed in 15 days accordingly activities will
be done like in 12 days website will be developed and after this testing will be carried
out. Requirements Doc: Project charter will be provided to each employee through whom
they can have all details while working on their aspects (Rew and et. al, 2020). Time Keeping: Each team member has to make sure that as per the plan they carry out
their operations otherwise it will not be possible to complete on time. Weekly PMIS Reports: This will enable team members to identify their performance with
respect to what is anticipated and what is attained. Meeting Agendas: Twice in a week meeting has to be conducted so that overall
performance can be analysed. Meeting Minutes: This involves what is being said in meeting and how further plans will
be work out (Sarmiento-Calisaya and et. al, 2020).
 Steering Committee: They will provide list of priorities which are needed for
working of a single aspect of the work.
 Technical Committee: Expertise will be involved who can give guidelines for
how well work is done and what can be done further to enhance quality of their
work.
Technical Design: Feasibility Study: This involves practicality of project like website is developed for
ecommerce shopping but if this is not possible then this means that project is not feasible.
 Data import mappings: This involves assigning or mapping data from database
field or any other source fields.
 Data export mappings: It will provide details of ways data within domain model
corresponds with JSON structure or XML schema (Sopahtsathit, 2020).

 Design Documents: This will furnish high level solution to developers with respect to
ecommerce shopping website they are developing.
 Design Overview: It implies summary or principles as well as elements that
outline visual content for website.
 Design for Servers: This comprises of servers required for hosting of website and
their configuration so that requirements of ample of customers can be
accomplished.
 Design for Database: It illustrates information that will be stored within a
database along with all the major aspects which has to be maintained (Tupeli,
2020). For developing ecommerce website MySQL can be used.
 Design Interfaces: It has to be a simple so that people can use it easily and text
present within this must be clearly readable.
 Design for Screens: They have to be user friendly with all the perspectives clearly
mentioned within them.
Testing: Unit Testing Checklists: This involves testing each components or unit of software to
ensure that each aspect works independently. For an instance user registration and when
they login into website have to be connected otherwise login credentials will not work.
Checklist for website involves writing class API, method for testing them,
implementation and launching unit test. System Test Checklist: This is carried on integrated system for evaluation that system
comply with peculiar needs (Zhai and et. al, 2020). Checklist comprises of creation of
system & acceptance test, its identification, creating work plan, formulation of test
approach and linking of criteria. User Acceptance Tests: With respect to ecommerce website, test will be carried out for
identification of requirements whether they are met or not.
 UAT for Servers: It will enable client to access website on peculiar server along
with this real-time view is being furnished.
 UAT Applications: This enables client to carry out acceptance testing with respect
to website that is being created (Zhang and et. al, 2020).

Training: Scheduling: The schedule will be formulated for giving training to clients or users who
will be making use of website like owner of ecommerce shopping website. Presentation Materials: Adequate material will be provided to ensure that all the
essential information is being provided. User’s Guide: Furthermore, a manual will also be rendered so that in case any kind of
problems is being faced by client then they can have solution quickly (Ali and John,
2020). Feedback Surveys: The developers can have feedback from owner of website with
respect to work done by them. It will be relevant for them to enhance their performance
but this has to be honest.
Risk Management Plan
The document which is being prepared by project manager for foreseeing risks,
estimation of influence as well as defining response for them is referred to as risk management
plan. Risk management involves detection, evaluation as well as prioritization which is being
followed through coordinated as well as economical usage of resources for minimisation,
monitoring and controlling influence of unfortunate events (Ferreira and Canedo, 2020). The
crucial aspects related with this are illustrated below:
Risk identification: The process associated with determination of risks which can
potentially thwart enterprise, program or investment from attaining their goals or objectives is
referred to as risk identification. With respect to website development, some risk is illustrated
below: Various decision makers: When different stakeholders are associated with project then it
can lead to bottleneck within decision making as well as having approval for same from
them.
 Custom coding to have features right: This implies that it is always not possible to
always be 100% right. Like if individuals are 90% right then for having 10% more they
might mess up things (Top 10 Website Project Risk Factors, 2020).
 Inaccurate project estimation: The clients of ecommerce website may underestimate
amount of time they have to invest within the project.

 Adding unnecessary features: Gold plating (addition of features which are not requested
in scope) is done.
 Application is not scalable: The website may crash due to incorrect memory usage,
browser incompatibity, incurable production bugs and many more.
These are some major risks which may be experienced by developers while developing a
website (Herrera and et. al, 2020). But after their identification, it is necessary that they must be
analysed.
Risk analysis: This involves identification as well as analysis of probable issues that will
negatively create an impact on key business projects or initiatives. The risks have been identified
in above step but it is necessary that they must be prioritised and accordingly resolved.
 Various decision makers: This is the major aspect as there are two owners and approval
from both of them is necessary. This has a top priority in numbering it can be 5 by 5 as
entire project is dependent on this aspect.
 Custom coding to have features right: It will have a strong impact on project thus it can
also be numbered 5 by 5. As if, developer gets to work on 10% that is not attained then
there is high probability that other features will be impacted.
 Inaccurate project estimation: Probability of this is less as compared to others, 2 by 5 as
developers specify this aspect when project is started (Kermanshachi and et. al, 2020).
 Adding unnecessary features: This has low probability 1/5 as normally people do what
is being given to them even they tend to skip some aspects.
 Application is not scalable: It is crucial and will have adverse impact 4/5 as website may
not run on clients system.
Risk planning:
 Various decision makers: Meeting with both the stakeholders can be held simultaneously
so clear scope can be attained.
 Custom coding to have features right: This aspect has to be left but it must be ensured
that 90% is working accurately and is able to accomplish scope of the project (Li,
Verhagen and Curran, 2020).

 Inaccurate project estimation: Initially when project is taken up and all the requirements
are understood then time required for its completion has to be decided but project
manager needs to ensure that 2 to 3 days are taken extra so that in any case any bug arise
then they have time to resolve it.
 Adding unnecessary features: Objectives must be clearly understood and each team
member must be provided with manual for that along with what they have to do.
 Application is not scalable: All the requirements have to be analysed when project is
taken along with this feasibility aspects must also be considered while developing
projects (Loehr, Suzuki and Mallick, 2020).
These are the steps which must be taken up by developers while working on ecommerce
website. It will enable to accomplish objectives of project as per required standards.
Software Requirements Specification
The document which is liable for capturing complete details about ways in which
system is anticipated to perform is defined as SRS.
User requirements: The document which illustrates anticipations of users with respect to
particular software. They are discussed when use cases for a project are written and are carried
out with project manager or customers to identify how system will be utilised by user. In this
case, the owner of website is users and their requirements will be acknowledged while
developing website (Raharjo and Purwandari, 2020). It has to be ensured that all the needs are
clearly stated and understood. Project manager will further illustrate them to developers so that
accordingly ecommerce website can be developed. User needs an ecommerce website for
shopping. This will involve registration of users, login option, preferences with respect to
shopping, online payment and wish-list.
System requirements: All the computer software requires certain hardware components
or other resources which must be present within system so that they can be executed effectively
on their device. This is called system requirements. The minimum hardware requirement is
system with 2Ghz minimum multi core processor, 4GB RAM or high, 10 GB hard disk space.
Software requirements comprise of an operating system Windows 7 or higher and drivers for Wi-
Fi enabled settings.
Functional & non-functional requirements: System or their components which
illustrates functions carried out by software refers to functional requirements (Rew and et. al,

2020). With respect to ecommerce website they involves maintaining details of their products,
users registration, make online orders, cancel them, make payments and an interface that can be
used by users.
Non-functional requirements refer to usability as well as efficiency of entire software
system. If these needs are not accomplished it clearly illustrates that system failed to accomplish
requirements of user (Sarmiento-Calisaya and et. al, 2020). In context of ecommerce shopping
website they comprises of security (like details of users cards are not compromised),
interoperability, availability, reliability, serviceability and capacity along with data integrity.
Use case diagram: The list of events or actions which defines communication among
actors and system for attainment of gaols is referred to as use case (Sopahtsathit, 2020). Here,
actor implies human who will be making use of a system.
Illustration 2: Use Case for Online Shopping

The use case for online shopping website has been illustrated above in which returning
customer can enter into website, manage their cart, delete or edit items and even add new.
Furthermore, they can view items and make purchase as per their requirements. They can make
payment by making use of credit card or PayPal then checkout. The new user can view items and
can register into system and they will be authenticated as well as provided by identity by identity
provider. Same can be done by them as it is carried out by returning user. Here, credit payment
service and Paypal are options provided to customers through which they can make payments for
their purchases. By carrying out these operations they can checkout from the system. The use
case easily elaborates the way in which customers will excess the website of ecommerce
shopping website.
Conclusion
Form the above it can be concluded that while developing a project it is necessary that
project management plan is formulated precisely by taking into account all the requirements of
system which has to be developed. Along with, SRS document must be maintained as a checklist
to ensure all the aspects are covered within this. As per project team has to be formulated who
will be responsible for managing entire process from its initiation till it is completed. WBS can
be used for dividing activities among team members along with this risk management plan needs
to be developed so that if any problems are identified then they have a backup for resolving
them. Furthermore, all the requirements have to clearly identify through system and user
requirements specification. In addition to this, use case can be utilised for doing so.

References
Books & References
Ali, M.Z. and John, S.J., 2020. Beyond Agile Boundaries. Lulu. com.
Ferreira, V.G. and Canedo, E.D., 2020. Design sprint in classroom: exploring new active
learning tools for project-based learning approach. Journal of Ambient Intelligence and
Humanized Computing, 11(3), pp.1191-1212.
Herrera, R.F. and et. al, 2020. Interaction between project management processes: a social
network analysis. International Journal of Project Organisation and Management, 12(2),
pp.133-148.
Kermanshachi, S. and et. al, 2020. Development of the project complexity assessment and
management framework for heavy industrial projects. International Journal of
Construction Education and Research, 16(1), pp.24-42.
Li, R., Verhagen, W.J. and Curran, R., 2020. Stakeholder-oriented systematic design
methodology for prognostic and health management system: Stakeholder expectation
definition. Advanced Engineering Informatics, 43, p.101041.
Loehr, J., Suzuki, H. and Mallick, P.B., Sun Patent Trust, 2020. Controlling ue behavior for
csi/srs reporting during drx. U.S. Patent Application 16/674,873.
Raharjo, T. and Purwandari, B., 2020, January. Agile Project Management Challenges and
Mapping Solutions: A Systematic Literature Review. In Proceedings of the 3rd
International Conference on Software Engineering and Information Management (pp.
123-129).
Rew, L. and et. al, 2020. Application of project management tools and techniques to support
nursing intervention research. Nursing Outlook.
Sarmiento-Calisaya, E. and et. al, 2020, March. Towards the improvement of natural language
requirements descriptions: the C&L tool. In Proceedings of the 35th Annual ACM
Symposium on Applied Computing (pp. 1405-1413).
Sopahtsathit, P., 2020. Software Analytics for Manual Activities using Developer Work
Elements. Journal of Information Processing, 28, pp.279-291.
Tupeli, A., 2020. A Requirements Specification Template for Temperature Calibration System.
Zhai, Z. And et. al, 2020. Visualizing the Knowledge Domain of Project Governance: A
Scientometric Review. Advances in Civil Engineering, 2020.
Zhang, X. and et. al, Qualcomm Inc, 2020. Delay minimization for csi-rs and srs transmission.
U.S. Patent Application 16/460,831.
Online
Top 10 Website Project Risk Factors. 2020. [Online]. Available through: <
https://www.itomic.com.au/top-10-website-project-risk-factors/ >.