Nguyễn Hòa Thuận THAI NGUYEN UNIVERSITY ICTU Subject: Software requirements analysis Topic: E-Commerce Website Group : Team 1 Class : KTPM K20 KNU Instructor: Nguyen Hong Tan Team Member: 1. Trần Khánh Duy 3. Nguyễn Hoàng Anh 4. Ma Quang Thiên Nguyễn Hòa Thuận Thái Nguyên,18th September 203 Table of Contents 2 Acknowledgements 3 Definition and Acronyms 3 INTRODUCTION 1 1.
Problem 2 SOFTWARE PROJECT MANAGEMENT PLAN 1 1. Software process model 6 2. Roles and Responsibilities 6 2. Project team member 6 2.
Tools and Techniques 6 3. Project Management Plan2 3. Project development plan 3 3. Communication plan 3 VISION DOCUMENT 1 1.
Definitions, Acronyms and Abbreviations 3 1. Product Position Statement 3 3. Stakeholder and User Descriptions 2 3. Market Demographic 3 2 Nguyễn Hòa Thuận 3.
Customer Service Department 6 3. Key Stakeholder or User Needs 3 4. Summary of Capabilities 3 4. Assumptions and Dependencies 3 4.
Liscensing and Installation 3 5. Precedence and Priority 2 9. Other Product Requirements 2 9. Non-Functional Requirements 3 SOFTWARE REQUIREMENT SPECIFICATION 1 1.
User Classes and Characteristic 3 2. Operating Environment 3 3 Nguyễn Hòa Thuận 2. Design and Implementation Constraints 3 2. Assumptions and Dependencies 3 3.
Registration and Login 3 3. Add to Cart and View Cart 3 3. Add and Update products 3 3. View Order Details 3 4.
External Interface Requirements 2 4. Use case diagram 3 5. Use case list 3 5. Use case description 3 6.
Other Nonfunctional Requirements 2 6. Software Quality Attributes 3 SOFTWARE DESIGN SPECIFICATIONS 1 1. Choice of Architecture design 6 2. Table Descriptions 3 4 Nguyễn Hòa Thuận INTRODUCTION 1.
Purpose Introduction chapter introduces the background and initial idea of the Capstone Project. In this chapter, we – the developing team – will provide information about what we do and the reasons why we do. Shopping has long been considered a recreational activity by many. Shopping online is no exception.
The goal of this application is to develop a web based interface for online retailers. The system would be easy to use and hence make the shopping experience pleasant for the users. Developing a website by PHP and mySQL can help users easily manage information on the electronic product. Project Information Project name: ShopHouse Website Project code: SH Project group name: Team 1 Product type: Website application Timeline: From 14th Feburary to 28th April 2023 3.
Supervisors Full name Phone E-mail Title Supervisor Nguyễn Hồng Tân Instructor 3. Team members No Full name Phone E-mail Role 1 Nguyễn Hòa Thuận 01679680722 5000thuan@gmail.com Leader 2 Hà Quốc Hữu 01217087170 HaHuu94@dumb.com Member 3 Ma Quang Thiên 0975842929 MaThue02@dumb.com Member 4 Trần Khánh Duy 0384493763 DuyLosKD69@dumb.com Member 5 Đặng Hoàng Anh 0968522114 HoangAnh92@dumb.com Member 5 Nguyễn Hòa Thuận 4. Background The history of ecommerce shopping carts began immediately after the World Wide Web or WWW, became a major medium to communicate information around the world. Ecommerce shopping-cart applications allow consumers to buy goods or services directly over the internet using a web browser.
This online shopping evokes the business-to-consumer (B2C) process where a consumer buys directly from the business. The process where a business buys from another business is called a business-to-business (B2B) process. The best examples of shoppingcart applications using B2B process are eBay and Amazon, both of which were launched in 1995. At present, most users of these online shopping-cart applications are people who have higher levels of education, have exposure to technological advancements, and are in a better income group.
Such users develop a positive attitude towards these convenient shopping techniques. According to a study in December 2011, Equation Research surveyed 1,500 online shoppers and found that 87% of tablet owners made online transactions during the early Christmas shopping season. Building a new successful shopping cart is simple because of high competition in the market, and the designer of a shopping-cart application must consider the information load complexity, and novelty. Complexity refers to the number of features available on the shopping cart and the levels of marketing, whereas novelty involves the unexpected or unfamiliar aspects of the site.
A designer must also consider the consumers’ needs and expectations. A user-friendly design is very critical to the success of any shopping-cart application because, unlikephysical stores, consumers at online stores come from all ages, genders, and cultures. Logistics clearly says that, to have a successful and profitable online shopping application, businesses have to spend a significant amount of time and money for designing, developing, testing, and maintaining the application. Apart from the high-class design and user interface, a good practice needs to be done to provide quality customer service.
Problem - The current system can be extended to allow the users to create accounts and save products in to wish list. - The users could subscribe for price alerts which would enable them to receive messages when price for products fall below a particular level. - The current system is confined only to the shopping cart process. It can be extended to have a easy to use check out process.
- Users can have multiple shipping and billing information saved. During checkout they can use the drag and drop feature to select shipping and billing information. 7 Nguyễn Hòa Thuận SOFTWARE PROJECT MANAGEMENT PLAN 1. Purpose Project Management Plan chapter helps readers to understand how our organization structures and view closer to the project plan.
All members must use this document to clarify each own responsibility. It also provides principles, which team members need to abide by during the whole time of developing project. Project organization Iterative and Incremental software process model We use Iterative and Incremental software process model – a method by which system is developed in small phases in a time and through repeated cycles. Developers can take advantage of this model through reviewing parts of system to change or improve them.
It also allows developers to receive feedback to modify the target of the next releases. The incremental and iterative development process is integral to the field of Agile software development as it enables project managers to reap the benefits of both incremental and iterative approaches. Incremental development ensures that 8 Nguyễn Hòa Thuận developers can make changes early on in the process rather than waiting until the end when the allotted time has run out and the money has been spent. Organization structure Organization structure 2.
Roles and Responsibilities Role Responsibility Project manager has responsibilities to plan, schedule and control the project. He Project manager has to communicate with all teams to keep them focusing on the final goal also. Technical leader has responsibilities to decide what technologies the project uses. Technical leader He works with business analysts to design system architecture and database.
Additionally, he supervises other developers working Document leader has responsibility to prepare all the documents relating to the Document leader project. Test leader has responsibilities to plan, monitor and control the testing activities Test leader and tasks, including setting up test, evaluating test run and recording test results 9 Nguyễn Hòa Thuận Developers have responsibilities to code product, review other developers’ code. Developer They set up, run unit test, receive bugs from testers and fix these bugs Testers have responsibilities to test product, write test cases for integration, Tester regression and acceptance test phases. They execute these written test cases, log bugs and inform developers.
Designer has responsibilities to design user interface of product, draw mock-up Designer screens for all user cases before implementing. Business analysts have responsibilities to work with project manager to analyze business domain, define functions and scope of system. They work as a bridge Business analyst between business problems and technology solutions. Project team member Team member Role Nguyễn Hòa Thuận Project manager, Document leader, developer Hà Quốc Hữu Technical leader, Test leader, developer Ma Quang Thiên Business Analyst, tester.
Trần Khánh Duy Document member, tester Đặng Hoàng Anh Document member, designer. Tools and Techniques Programming languages Php IDEs/Editors Visual Studio Code UML tools Draw.io, Edraw DBMS MySQL Project management Microsoft Project 2016 tool Design tools Astag Professional, Microsoft Visio 2016 Communication tools Facebook, Zalo, Google mail. Web browser Google Chrome, Mozilla Firefox, Opera GX 10 Nguyễn Hòa Thuận Process model Iterative and Incremental Software Process Model 3. Project Management Plan 3.
Risks Management No Description Avoidance plan Contingency plan Impact R1 Absence/illness Members have inform The project manager High of team members the project manager the always has back up plan reason why they are to avoid effect from the absent and build their absence and ensure that own plan to keep up problem will be solved with the work process. R2 Conflicts among At the beginning, The project manager has Medium members members should clear to find out the root that their roles and caused problem and responsibilities. Face-to-face meeting is a good method. R3 Business Any ideas are welcome Making sure that the High problem but members have to business logic of any discuss with others and ideas is carefully always focus on the analyzed.
reality and possibility. R4 Change Analyzing requirements If there is a “must be High management carefully. changed” requirement, overload all team members must join the meeting to decide whether it should be implemented or not. R5 Equipment of Members must be Members should use Low members is careful with their another equipment until broken equipment.
the broken one is fixed or buy the new one R6 New Choosing technology When the technical High technologies based on members’ leader chooses a new qualification. All team technology, he has to members must nurture explain to all team 11 Nguyễn Hòa Thuận by self-study. members about the decision. R7 Project team Members have to read Making sure that any Medium member requirement miscommunication misunderstands specification and related would be resolved requirements documents carefully.
R8 Lack of data to Making plan to train Classify data into some Medium train data everyday categories and make sure that each category contains enough data High R8 R1, R3 Probability Medium R6 R7 R2, R4 Low R5 low medium high Impact 3. Project Pevelopment Plan Project Development plan-1 12 Nguyễn Hòa Thuận Project Development plan-2 3.Communication Plan Planning Phase: team meeting was held twice per week (Monday and Friday). Face to face meeting is the most effective way for team member to understand and clarify detailed requirement. Output of each meeting is a meeting minute to keep up important information.
Implement Phase: All members implement all task that PM and technical leader assigned on Every week, on Monday, there will be have a meeting when each team member report to the whole team what he did the previous week, then all member plan the schedule for upcoming week, and solve the issues together. Communication Channels: Gmail. Instant message: Messager. Phone: in urgent emergence, phone is a good ways to share the idea.
Face to face meetings 13 Nguyễn Hòa Thuận Vision 1. Purpose The purpose of this Vision document is to capture the focus, stakeholder needs, goals and objectives, target markets, user environments, target platforms, and features of the product to be built. It communicates the fundamental "whys and whats" related to the project, and it is a gauge against which all future decisions should be validated. Scope The vision document provides an overall understanding of the system to be developed by providing a self-contained overview of the system to be built and the motivations behind building it.
This document focuses on understanding the goals of E-Store which has aligned itself with the corporate strategic priority to become a leading e-Business company and to leverage the power of e-Marketing, e-Sales and e-Services. Definitions, Acronyms, and Abbreviations Acronym Definition Catalog Classification and description of all products on sale. Database A database is a structured collection of records or data which is stored in a computer so that a program can consult it to answer queries.