· The project is about providing the products to the target market and generating revenues at a high level. The project’s objective is to increase the company’s revenues to $30 million and have 30 employees from $10 million and ten employees, respectively. It solves a principal problem in the medical field and provides an alternative to the organization as the start-up (without having a physical infrastructure).
· The project solves the problems of people with arthritis and osteoarthritis. From a business point of view, the project ensures the revenue stream of the company. It is the primary step to establishing the business to ensure and start the generation of revenues by increasing market presence and allowing the customers to be aware of the products of the company.
· The goals of the project are to:
i. Spread awareness about the company to the customers.
ii. Increase business revenues.
iii. Build a successful and secure platform for the sale of the products of the company.
· Information technology plays an integral role in the project. As it is a start-up and the initial action of the company is to design and implement an e-commerce website, the use of technology is the backbone of the project. The software part of the project is related to IT. E-commerce and information technology are closely related. IT has the power to develop the industry and its transformation of the running of the business.
Functional Business Requirements (Scope) and Scope Control
The business’s functional business requirements or scope provides an overview of the outcome of the project results. The functional part of the statement deals with the features or functions of the product, which must be considered and implemented by the developers for ensuring the accomplishment of the tasks. Thus, it is very important to clearly describe the functional requirements to the stakeholders and development team. The functional requirements depict the behavior of the system under specific conditions. The functional requirements in the case of developing the e-commerce website are software requirements specifications documents. It presents certain details of use cases and user stories. Use cases include an overall view of the connection between different actors of the project, their use cases, and the overall system. Acceptance criteria must accompany the user stories. The INVEST quality model (Independent, Negotiable, Valuable, Estimable, Small, and Testable). It also includes the work breakdown structure, which allows allocating the activities concerning time and their respective resources. The prototype is also included in the functional requirements. The prototype of the website also covers the design documentation of the process. The models and diagrams required are also included in the process. It includes Wireframes, Mockups, and Design prototypes.
To meet the target production date, only these applications will be implemented:
These sites are considered part of the implementation payment tabs and product sites.
In addition, while the development of the e-commerce website
Re-engineering will be done if there is any mistake or flaw in the system
Proper re-checking of the system, maybe taking help of an external consultant
Customizations will be limited to the designs and layout of the website
Graphic designing and website development will take care of these customizations
Interfaces included are a User-friendly UI and graphical user interface.
Proper utilization of the interface and their monitoring
Application and technical architecture will be client-server architecture.
Effective and successful architecture building
Use of effective technical skills
Only the following data and volume will be considered for conversion:
Testing will include only the testing of the final stage of the e-commerce website after development.
Testing in different situations and under different circumstances for exploring issues like security.
Project funding is limited to less than 10 million as the company’s total revenues are 10 million.
Proper cost management strategies.
Evaluation of the expenditure on the
Training will be provided to the employees to properly use the website, navigation of the orders, and the overall system.
Development of the training course
Scheduling the training of all ten employees
Education will include the resources available to the staff to learn more about the e-commerce platform and its functioning.
Providing resources to the staff members
Easy access to the resources
Change control will manage changes to the scope identified in this document. Any changes affecting project costs and timelines require business owner approval.
Non-functional Business Requirements (Governance, Risk, Compliance)
Non-functional business requirements related to governance include:
· Compliance includes governance of IT regulatory compliance.
· The successful architecture of the enterprise.
· Financial governance
· Information governance
· IT processes
Non-functional business requirements related to risk include:
· Security of the e-commerce websites
· Interpretation of the platform with the software available in market
· High cost of implementation.
Non-functional business requirements related to compliance include:
· Meeting the security standards
· Conforming to the legal and ethical rules such as policy, specifications, or laws
· Compliance with the internal and external standards of the parties.
· Data integrity
Technical Requirements for Integration of E-commerce Components (1 page)
The other components include the standards required to be followed by the designers and engineers working on the project. The analytics of the system includes three or more types of analytics. These can be web analytics, text analytics, big data, and others. The hardware components used for the project are information security and repository. These are all the physical setups used in the project, including firewalls, servers, encryption devices, coding hardware, and others. Thus, the most important technical requirements necessary to integrate the e-commerce components are hardware and software components.
Potential Risks, Constraints, and Assumptions
Risks are the dangers or threats that can occur to any project. The risks can cause a postponement or termination of a project. Thus, it is important to identify the risks at the beginning of the project. Risk identifications give the project managers a chance to go over the mitigation steps that help reduce the severity of risk, which helps reduce the impact on the project’s overall performance. Project risks can be related to resources, either human, financial, or physical, scope, time, cost, and other related factors. The aim is to reduce the level of negative risks as low as possible. Risks associated with the current project and their respective mitigation strategies are provided in the table below:
Risk #1: Shortage of time
Proper time management
Review of the activities and their allocated time
Reviewing the completion of milestones concerning delivery time.
Issue with the computer systems or coding
Ensuring the working of the computers
Ensuring the coding skills of the staff
Risk #3: Lack of resources
Proper allocation of resources, either human or financial.
Management of resources in an effective manner throughout the project
Risk #4: Inability to understand the requirements
Ensuring the understanding of requirements in the earlier stages of the project.
Double-checking by giving and taking a presentation with employees.
Ensure effective communication strategies
Risk #5: No control over staff priorities
Making sure of the loyalty of the staff to the project
Ensuring the alignment of the professional objectives of an employee with that of company’s
Constraints are the postulates or points which are the limitations of a project. They provide the narrowed lines for the projects that must be respected. A project is always surrounded by various constraints, either due to the company’s situation or affected by one or more of the stakeholders. The most significant constraints facing the e-commerce start-up project are mainly due to the company’s limitations and resources and resources. Most of the time, the project constraints are linked with each other. These constraints have been identified:
· Proper definition and understanding of the scope of the project is a constraint.
· The limited time applied by the organization is 60 days.
· The budget limitation due to the narrowed total revenues of the organization.
· The potential risks to the project are the constraints of the project.
The project must be completed keeping in mind all these constraints.
The most significant assumptions related to defining this project scope, objectives, and approach scope include:
· The project will be completed within the allocated time.
· All the resources required for the project will be available.
· All the human resources will have the required skills and will understand the project scope completely.
· All the objectives of the project will be met with the required resources.
· The project will be able to generate double revenues for the company in the next two years.
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.Read more
Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.Read more
Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.Read more
Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.Read more
By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.Read more