Topic Name Completing The Required Specification Document For The Website To Sell Girl Clothes..pdf

HANOI UNIVERSITY OF INDUSTRYFACULTY OF INFORMATION TECHNOLOGY

Phan Kim SinhNguyễn Xuân HàMa Thị LợiĐoàn Hữu Minh

Class: 20221IT6082001

HaNoi - 2022

MỤC LỤC

CHAPTER 1 Overview of software engineering 2

1.1 Basic concepts 2

1.2 Compare the difference between the design models 4

CHAPTER 2 Structure of a Requirements Document 11

2.2.5 Assumptions and Dependencies 20

CHAPTER 3 Specifific Requirements 21

Information technology in the current period is developing like a stormin all fields of operation in all parts of the world Informatics is one of theindispensable issues for any organization or company Decimal and integralrequirements are critical to the work of a project and are the first technician'ssoftware development process When performing requirements analysis andcollection, external requirements files from customer evaluation, analysis areextremely necessary and standard requirements Especially with the processof improving requirements, upgrading the system, it is necessary to evaluateand analyze based on the current system Special about the system and relateddocumentation to the development of the system will become extremelynecessary and the owner, when the job of managing the characteristics andrelated documents is done well the analyzer Accurately and quickly, is thefoundation for the analyzer to analyze the impact on the system when thereare upgrade requirements and improvement processes.

With the study of subject knowledge under the guidance of lecturer Ms.Nguyễn Thị Mĩ Bình, our group made a large exercise report on “Completingthe required specification document for the website to sell girl clothes” tospecify the services that the website system provides and the constraints tobuild and operate a website selling clothes From surveying the system todetermining the functionality and data model of the website, the team in turnconducted a detailed analysis and specification of the Shein.com.vn websitewith the aim of determining the responsiveness of the website with customerswho visit the website.

CHAPTER 1 Overview of software engineering1.1 Basic concepts

Definition of software:

Software is a set of computer programs and associated documentation anddata This is in contrast to hardware, from which the system is built and whichactually performs the work.

- Embedded Software: This type of software is embedded into thehardware normally in the Read-Only Memory (ROM) as a part of a largesystem and is used to support certain functionality under the controlconditions Examples are software used in instrumentation and controlapplications like washing machines, satellites, microwaves, etc.

- Business Software: This category of software is used to supportbusiness applications and is the most widely used category of software.Examples are software for inventory management, accounts, banking,hospitals, schools, stock markets, etc.

- Web Applications Software: Networking Software provides therequired support necessary for computers to interact with each other and withdata storage facilities Networking software is also used when software is

running on a network of computers (such as the World Wide Web) It includesall network management software, server software, security and encryptionsoftware, and software to develop web-based applications like HTML, PHP,XML, etc.

- Artificial Intelligence Software: Software like expert systems, decisionsupport systems, pattern recognition software, artificial neural networks, etc.come under this category They involve complex problems which are notaffected by complex computations using non-numerical algorithms.

Attributes of good software:

+ Good functionality and high performance.+ Maintainable.

+ Reliable.+ Reusable.

Life cycle of software development:

Definition: Software Development Life Cycle is the application of standardbusiness practices to building software applications It’s typically divided intosix to eight steps: Planning, Requirements, Design, Build, Document, Test,Deploy, Maintain Some project managers will combine, split, or omit steps,depending on the project’s scope These are the core componentsrecommended for all software development projects.

There’s 3 phase in software process:+ Definition phase

+ Development phase+ Support phase

Framework of software development:+ Process framework

+ Umbrella activities+ Software engineering action+Task set

1.2 Compare the difference between the design models

Phases in the waterfall model:

The steps in the waterfall model include:

Requirement Analysis: All possible requirements of the developedsystem are documented in this phase and documented in the requirementsspecification document to serve the requirements later stage;

System Design: The required specifications from the early stage arestudied in this phase and the system design is prepared This system designhelps to define hardware and system requirements as well as helps to definethe overall system architecture;

Implementation: With input from the system design, the system is firstdeveloped in small programs called units, which are integrated in the nextphase Each Unit is developed and tested for its functionality (also known asUnit Testing);

Integration and Testing: All the units developed during the deploymentphase are integrated into a system after testing of each unit After integration,the whole system is checked for any errors and failures (this stage is alsoknown as integration testing).

Deployment of system: After functional and non-functional testing isdone; the product is deployed in a customer or marketed environment;

Maintenance: There are some problems occurring in the customerenvironment To fix those problems, patches are released Also to enhance theproduct several better versions are released Maintenance is performed tobring about these changes in the customer environment.

Figure 1.1 Phases in the waterfall model.

The iterative approach model:

Figure 1.2 Phases in the Iterative modelRequirement: Analyze and define software requirements:Build 1: Simple deployment with a small set of requirements.

Build i: Improves the previous version by adding requirements to create anew version.

Build n: The final stage of building a complete software version with fullsoftware requirements.

The basic idea behind this approach is to develop a system throughcycles iteractively (iteration) and in smaller pieces at a time (incremental).The iterative process begins with a simple implementation of a subset of the

software requirements and iterative improvement of the versions indevelopment until full system implementation At each iteration, designmodifications are made and new functional capabilities are added.

From there, we can clearly see some advantages of the incrementalgrowth model:

- After each round increase, the performance results can be transferred tothe customer so the system functions can be seen sooner.

- The previous rounds act as a prototype to help learn more requirementsin the next rounds.

- The higher the priority system functions, the more thoroughly tested.Spiral pattern:

Phases (working areas) are divided into arcs Each variant of the spiralpattern can have 3 to 6 regions.

Figure 1.3 Spiral model includes 6 working areas.

Contact, communicate with customers: between developers and customersto find out requirements and opinions;

Planning: estimate; planning;Risk analysis;

Technical execution: Build one/several representations of the applicationBuild and release: Code, test

System evaluation: Customers participate in system evaluation

Figure 1.4 Spiral model includes 6 working areas.Contact, communicate with customers: between developers and customers

to find out requirements and opinions;Planning: estimate; planning;

Figure 1.5 illustrates the spiral model with 4 working areas.

Figure 1.6 illustrates the steps in a spiral model with four workspace.

Figure 1.5 and Figure 1.6 are illustrations of the spiral model with fourworking areas:

Define goals and identify alternatives: Requirements are collected fromthe customer and goals are identified, developed and analyzed at the startof every phase Then the possible alternatives for the stage are suggestedin this quadrant.

Identify and Address Risks: In the second quadrant, all possible solutionsare evaluated to select the best possible solution.

Development of the next version of the Product: In the third quadrant, theidentified features are developed and verified through testing At the endof the third quadrant, the next version of the software is available.Review and Planning for the Next Stage: In the fourth quadrant, the

Customer evaluates the developed version of the software to date Finally,planning for the next phase begins

The waterfall model is simplest process model, which states that thephases are organized in a linear order In a waterfall model, each phase mustbe completed before the next phase can begin and there is no overlapping inthe phases the waterfall model has been the most widely used process model.It is well suited for routine types of projects where the require-meets are wellunderstood That is, if the developing organization is quite fa-mi liar with theproblem domain and the requirements for the software are quite clear, thewaterfall model works well, and may be the most efficient process.

In the Iterative model, iterative process starts with a simpleimplementation of a small set of the software requirements and alliterativelyenhances the evolving versions until the complete system is implemented andready to be deployed An iterative life cycle model does not attempt to startwith a full specification of requirements Instead, development begins byspecifying and implementing just part of the software, which is then reviewedto identify further requirements This process is then repeated, producing a

new version of the software at the end of each iteration of the model Iterativemodel is used when the software application is large.

The spiral model combines the idea of iterative development with thesystematic, controlled aspects of the waterfall model This Spiral model is acombination of iterative development process model and sequential lineardevelopment model i.e the waterfall model with a very high emphasis on riskanalysis It allows incremental releases of the product or incrementalrefinement through each iteration around the spiral The spiral model ispreferred for large, expensive and complicated projects

=> The variety of models today brings a lot of options Softwareprogramming units need to base on their development needs to apply theappropriate model.

CHAPTER 2 Structure of a Requirements Document 2.1.Introduction

2.1.1 Purpose

Today, information technology has made strong development steps, becoming more and more comprehensive to meet many human needs Smart electronic devices such as phones and computers have become a part of people's lives.

Faced with the fierce competition of information technology, organizations and businesses are looking for every measure to build and perfect their information systems in order to computerize their operations Currently, the world's leading IT companies are constantly investing and improving solutions and products to enable commercialization on the Internet.

Through these products and technologies, we easily realize the

importance and inevitability of e-commerce With simple operations on smart electronic devices connected to the Internet, you will be able to find out and buy what you need without spending much time You just need to go to the e-commerce service pages, follow the instructions and click on what you need Service providers will bring the product to your home.

In order to approach and contribute to promoting the popularity of commerce in Vietnam, we decided to carry out the topic "Writing a specification document for the website selling SHEIN women's fashion products"

e-2.1.2 Scope

Scope of production.

Target customers: men, women, children, household appliances.

Product type: pants, tops, skirts, spare shoes, beachwear, underwear.

2.1.3.Definitions, Acronyms, and Abbreviations

Use case Diagram depicting system requirementsWeb server The server software provides the functions

capabilities, resources for the client

With the structure is divided into three parts:1 Part 1: Provides an overview of SRS components.

2 Part 2: Describe the overview of factors, binding, user characteristics, environment Execute the system and its requirements Provide detailed information

Functional requirements, providing software developers to distribute Software development meets those requirements.

2 Part 3: Non -functional requirements

2.2.Overall Description2.2.1 Product Perspective

The system consists of the actors Customer and Administrator.Customers have role is a user who can use the system without logging in orcan log in to use more system functions.

Administrators has the role of administering the operation of the system

Analyze user characteristics in SHEIN Website.

When entering the system, the user can perform the following functions:- Log in

- Register

- Add product to cart- Purchase

- Pay

Describe in detail each user's functional characteristics:

+ Login:

When you want to perform many functions in the website as a user, youmust be logged in The system will allow users to login in 2 ways as shownbelow:

Figure 2.1 : Illustration of the login functionThe first way :

Users will fill in 2 fields of information "email" and "password" If oneof these fields is missing, the user cannot log in When both fields are filledin, the system will verify that if both fields match, the user has successfullylogged in.

Second way:

Instead of having to enter information like in the first way, for thesecond way, users only need to choose 1 of 2 ways to log in, with Google orwith Facebook.

+ Sign up :

If this is the first time visiting the website, then the account registrationfunction is an indispensable function for users It allows users to create anaccount and with that account, users will forever use this website.

Figure 2.2 : Illustration of the sign up functionThere will be 3 required fields that the user must fill in:

+ Purchase:

To be able to complete the purchase process, the user will go to theshopping cart and select the item that he wants to pay for by clicking the "PayNow" button.

Figure 2.4 : Description of purchasing function+ Payment:

After clicking the "Pay Now" button, the user will come to the finalprocess to complete his purchase.

There are 2 forms of payment:+ Pay on receipt+ Online payment.

- Payment on receipt of goods:

For the form of direct payment upon receipt of goods, the user must fill inall his required information accurately:

Figure 2.5 : Description of fields to be filled in

When completing this information, the user will click on the "SAVE"button Orders will soon be delivered directly to users.

Online payment:

For the online payment form, the user will first choose one of theonline payment methods as he or she wants For this form, the user will stillfill in the necessary information to complete the process order The user willthen pay directly for the order to complete his purchase.

Picture 2.6 : Description of online payment methods.