SDLC Assignment 2 Bach Khoa, Study notes of Software Project Management

dadasdadasdasdasdasdsadasdasdasdasdasdasdasdasdasdasd

Typology: Study notes

2022/2023

Uploaded on 09/24/2022

kaio-ken
kaio-ken 🇻🇳

3.8

(4)

5 documents

1 / 33

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
PROGRAM TITLE: BTEC in Computing (Software Engineering)
UNIT TITLE: Software Development Life Cycles
ASSIGNMENT NUMBER: 2
ASSIGNMENT NAME: Software Development Life Cycles
SUBMISSION DATE: 07/07/2022
DATE RECEIVED: 07/07/2022
TUTORIAL LECTURER: Pham Son Tung
WORD COUNT: 4497
STUDENT NAME: Hoang Van Hiep
STUDENT ID: BKC 12227
MOBILE NUMBER: 0866814728
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21

Partial preview of the text

Download SDLC Assignment 2 Bach Khoa and more Study notes Software Project Management in PDF only on Docsity!

PROGRAM TITLE: BTEC in Computing (Software Engineering) UNIT TITLE: Software Development Life Cycles ASSIGNMENT NUMBER: 2 ASSIGNMENT NAME: Software Development Life Cycles SUBMISSION DATE: 07/07/ DATE RECEIVED: 07/07/ TUTORIAL LECTURER: Pham Son Tung WORD COUNT: 4497 STUDENT NAME: Hoang Van Hiep STUDENT ID: BKC 12227 MOBILE NUMBER: 0866814728

Summative Feedback: Internal verification:

A. Introduction

  • There are many different lifecycle models available for the methodical development of computer projects and software in the modern era of software development. Theoretical direction for software development is offered by SDLC models. Software development life cycle (SDLC) models are crucial for methodically creating software that will be delivered on schedule and with the required level of quality. These models are ideal for the circumstances of software development and particular types of software since they have unique qualities. Depending on the development context, one software lifecycle model may prove more effective than the other. The purpose of this research is to assess several software lifecycle models from this angle. Project managers can modify the overall software development strategy by selecting the appropriate SDLC. Each SDLC has benefits and drawbacks, and we must choose which model to use according on the situation. We will offer a thorough analysis of numerous life cycle models in this paper, including waterfall, sequential, repeat, prototype, spiral, incremental, etc. models. B. Content I. Undertake a software investigation to meet a business need
  1. Questionnaire Technique
  • A questionnaire is a research technique consisting of a series of questions for the purpose of gathering information from respondents.
  • Questionnaire can be thought of as a kind of written interview. They can be carried out face to face, by telephone, computer or post
  1. The reason for using questionnaire technique:
  • The responses are gathered in a standardised way
  • Information can be collected in short period of time from a large number of people, often geographically dispersed.
  • Inexpensive way to reach a large number of people
  • Standard questionnaire providers quantifiable answers to a research
  • Questionnaires allow respondents to take time to consider their responses carefully without interferences from others or interview
  1. Steps to approach data finding with questionnaire
  • Steps 1: Determine what information we would like to obtain
  • Steps 2: Decide what is the audience for your questionnaire
  • Steps 3: Decide on data collection method
  • Steps 4: Decide on types of question
  • Steps 5: Pilot the questionnaire on a sample of potential respondents and revise questions if necessary
  • Steps 6: Distribute the questionnaire
  • Steps 7: Chase non-responses
  • Steps 8: Analyse the responses
  • Steps 9: Present and use the findings
  1. Interview question Types of question Questions Closed-ended question Are Tune Source customers comfortable to use the new system? Would you please answer some questions? Does Tune Source have old customer data? What additional information do you want the new system to provide? How many records are sold per day? What do you think about the current system? How do customers make an order? Open-ended question What is the company’s desire for this new

A functional requirement defines a system or its component. A non-functional requirement defines the quality attribute of a software system. It specifies “What should the software system do?” It places constraints on “How should the software system fulfil the functional requirements?” Functional requirement is specified by User. Non-functional requirement is specified by technical peoples e.g. Architect, Technical leaders and software developers. It is mandatory. It is not mandatory. It is captured in use case. It is captured as a quality attribute. Defined at a component level. Applied to a system as a whole. Helps you verify the functionality of the software. Helps you to verify the performance of the software. Functional Testing like System, Integration, End to End, API testing, etc are done. Non-Functional Testing like Performance, Stress, Usability, Security testing, etc are done. Usually easy to define. Usually more difficult to define. Examples The software automatically validates customers against the ABC Contact Management System Users must change the initially assigned login password immediately after the first successful login. Moreover, the initial should never be reused. The Sales system should allow users to record customers sales Employees never allowed to update their salary information. Such attempt should be reported to the security administrator. The background colour for all windows in the Every unsuccessful attempt by a user to

application will be blue and have a hexadecimal RGB colour value of 0x0000FF. access an item of data shall be recorded on an audit trail. Only Managerial level employees have the right to view revenue data. A website should be capable enough to handle 20 million users with affecting its performance The software system should be integrated with banking API Privacy of information, the export of restricted technologies, intellectual property rights, etc. should be audited. The software system should pass Section 508 accessibility requirement. The software should be portable. So moving from one OS to other OS does not create any problem. 5.3. Functional and non-functional Requirements in project 5.3.1. Functional requirements

  • Client interface
    • Search product: the software filters and displays the products the consumers are seeking for once the buyers enter keywords.
    • View Product: Show all items in each category. Display categories in the menu using the category module.
    • Comment: Customers who want to comment will do so and the product section will be displayed.
    • Cart: generate payment invoices
  • Admin interface
    • Login: successful system login when the entered username and password are accurate
    • Product management module: add, edit, delete products
    • Category management module: add, edit, delete categories
    • Comment management module: delete comments that violate banned keywords
    • Order management module: add, update, delete and confirm orders

range from 65 to 75 percent of the total effort required to develop a software. Consequently, a software's maintenance is likewise of utmost importance.

  • Security: is correlated with the system's overall data security level. Businesses are very worried about security issues and preventing information loss. Delegating user permissions and having access to the system are also factors in security. I have solutions for system threats like spam, malware, a lack of security protocols, or hacker attacks to steal user information, such as updating website application software frequently, preventing sql injection, handling DDOS attacks, approving / validating server-side website security, using HTTPs, etc. With the use of these security measures, it can be said that the website will be reliable and not leak customer or store information. When working with customers, I will employ software that necessitates the usage of strong passwords, such as those with long characters, punctuation, etc. When that happens, it will be challenging for outsiders to access the customer's account by themselves. password
  1. Hardware/server requirements
  • Server configuration used to maintain the website:
  • CPU 1 x E5-2600 V4 (E5-2680V4, E5-2683 V4, E5-2686 V4, E5-2690 V4)
  • Ram: 128GB DDR
  • Hardware: 2 x 960GB and 2 x 900GB SAS 12G 10k
  • Raid: H730 / H
  • Network speed: 200Mbps
  • Bandwidth: Unlimited
  • Ip route: 02
  • Server Administration: Free
  • Configuring iDrac: Yes
  1. Project cost No Categories Cost Payment frequency 1 Domain $18,19 1 month 2 Hosting $107 1 year

3 Design and development $427, 4 Server $157,93 1 month 5 Testing $85, 6 Maintenance $85,6 1 year 7 Maintain SSL $21,4 1 year 8 Advertisement $85,6 1 month 9 Upgrades, bug fixes Free 1 year 10 Server location $59,92 1 month II. Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation.

  1. Stakeholder 1.1. Stakeholder #1: The client
    • The customer is the most highly interested and influential stakeholder, as they are paying for the services that a digital agency (or whoever is building the website) offers. As a result, you should treat their feedback with priority and make sure they have a positive experience throughout the project.
    • Customers can be both external or in-house, the difference being that external customers are unconnected businesses seeking the services of an agency in order to have a website built for them. The other type are in-house clients, which are basically other departments within an organization who are either looking for a new website or a redesign of an existing site.
    • If the customer is an external organisation seeking the expertise of a digital agency, it is likely that they will be represented by the business’ marketing department. They most likely already have an exact vision of their end goal. And due to this it is extremely important that this vision is communicated effectively in order for their needs to be met.

t page the product management page where the product has been corrected, the updated information will be saved in the database and displayed on the customer page. 3 Add product module Add new product information Fill in new information in the product information form Show newly added products on product managemen t page If you have finished adding new products, you will return to the product management page and the new products will be displayed, updated in the database and updated to the customer page. 4 Delete product module Delete product Check the selected product data for deletion The message that the product has been successfully deleted will appear and return to the If the product has been deleted, returning to the management page will no longer have the deleted product, it will no longer

managemen t page appear in the database, and the deleted product will no longer be visible on the customer page. 5 Add category module Add new information to the category Fill in new information in the catalog information form Display the newly added category in the category managemen t page If you have finished adding new products, you will return to the catalog management page and the new category will be displayed, updated in the database and updated to the customer page. 6 Update Category module Update new information for the list to be corrected Delete old information and change it to new information for the category Display new information on the edited category on the catalog managemen t page If you have completed editing the catalog information, you will return to the catalog management page where the product has been edited, the updated information will

customer page. 9 Add order module Add new order information Fill in the customer's purchase and sale information in the form Display the newly added order in the order managemen t page If you have finished adding new products, you will return to the catalog management page and the new categories will be displayed and updated in the database. 10 Update order module Edit order information Delete old customer information, fill in new information Display new corrected information in order managemen t page If the product update is completed, the product will return to the order management page, the newly corrected order will be displayed and updated in the database. 11 Confirm order module Confirm order information Check if the order information is complete Confirmed display on order managemen t page If the order does not match the quantity in stock, or the customer wants to change the address, cancel the order, the

order will not be confirmed or will be deleted, if the order is correct compared to the stock or customer needs. then the order status will be changed to "confirmed". 12 Delete order Delete order Check order data to be deleted from the database and order management page There will be a notification that the order has been deleted and the deleted order will not appear on the order managemen t page If the order has been deleted, the order will be returned to the order management page and the order will also be deleted from the database.

  • User No Descriptor Input Processes Output Processes Descriptor 1 Searching bar Enter product keywords Check product keywords Show products included in the keyword When the user enters a keyword in the search bar, the products with
  • Level 1 (Admin)
  • Level 1 (Customer)

4. ERD