(Solved) Assignment on SRE
Added on 2021-06-17
11 Pages2615 Words122 Views
|
|
|
SRE Assignment 3Page 1Assignment 3.Student name, s-ID:Student name, s-ID:Part 1. Traditional Way: SRS1.System Features1.1Messages and reminders:The messages and reminder feature displays the information about the current sales, if the user only is neat to the corresponding store. Then user when approaching the mega then the welcome message is displayed. Reminders are used for the discount purpose and for the loyalty programs. This only be done when the user is in the corresponding store. Reminder informs about the pick-up of the orders that are came online. Reminders are given based on the patterns of the previous solution (Lai and Ali 2013). Functional RequirementsFunctional requirements are those are associated with the function. A requirements is that the system displays messaged and the corresponding information about the sales to the user whether the user is in the store or the user is near the store. The EARS approach is called the easy approach to requirements syntax. The sender must be aware of the error message and the reminders. For any kind of reminders if there is an invalid input so this need to be corrected for any kind of error message which needs to be generated. 1.2Store location: This feature of the SRS advices the users to find the particular store within the mega. This will help the user of the corresponding store to be close to the store or is in the store (Rao and Srinivas 2015).Functional Requirements: These store location is associated with the mega app. The ability of the store locatingis applied to display a map of the mega center of shopping with a display which shows and
SRE Assignment 3Page 2directs the user about which store is located where. This will help the user to find the desiredlocated store. If there is any error occur in the display then the user will go to the wrong store in place of the actual store. This will save the time of the user as all as the stores will benefited. 1.3User behavior:User behavior is one of the system feature of the SRS. User behavioral requirements are displayed using the use case diagram. Using the use case diagram the total overview of the system is displayed. The use case diagram shows the user activities within the store of the mega (Chhabra et al., 2015). The functional requirements of the user behavior describes the functions of the user and the components that are user use. The requirements are the behavior and the input that are given by the user in the system. User behavior can be contrasted with the non-functional behavior. User behavioral feature is used for the user activity and described by the use case diagram. The user behavior are collected and presented to the managers in the application ofthe web on the information. 1.4Account management and wish list:In this feature the customers can edit their personal information on the account and then the user creates their wish list. The user can add or remove the items from their wish list anytime. These can be done during the website browsing. After adding the item in the wish list the user will get a notification of the wish list (Tarmizi 2013). This requirement does not mapped to any of the project objectives or the principles. There is no difficult or easy benefit of implementing this functional requirements. This only being done as the favor or if it is in any others wish list. This functional requirement can be dropped without having any negative impact on the total project or in the entire system. 1.5Advertisements Update:This feature that is advertisement update that is the information about the advertisement is updated via the web application. The srs document is created for the management system of advertisement. This is a solution that is online and the users who want to advertise their content in the web can do it online. This document consist of the overall information of the system and about the development of the system and testing is also described in the document (Lloyd‐Lavery et al., 2017).2.Nonfunctional RequirementsThe non-functional requirements are divided in to two parts one is internal quality another is external quality. The external quality is what that is primarily important to the users and it shows the quality in use. The external quality consists of availability,
SRE Assignment 3Page 3reliability, performance, robustness, safety, security, usability, integrity, instalability and interoperability. The internal quality is the most significant to the development and to the staff maintenance. The internal quality contributes to the satisfaction of the customer by making the product easier to enhance, test, correct and migrate to the newer platforms. The analysis of the attribute of the quality the following needs to me done:Firstly have to list a set of quality attributes to consider and the attributes has to be rich. Then we have to reduce the list by analyzing the view of the stakeholders and by recording the rationale that is used for deciding those particular quality attributes that are taken for the consideration. In the next step we have to prioritize the attributes by using the given Brosseau’s spreadsheet. The priorities are different for the users and for the staffs of the maintenance and for the technical staff. Then we have to elicit the specific expectations for the each attribute that the software must be user friendly, reliable, fast and robust.Then have to specify the well-structured requirements qualities. SMART approach is to be used that is Specific, Measurable, Attainable, Relevant, Time-sensitive.QualitiesRationalInternalReusabilityNot important, as we are not going to reuse any parts of this system in other solutions.MaintainabilityHigh priority, as this would help to increase availability by reducing the maintenance timesModifiabilityMedium priority, as we assume that the possibility of major changes is very low.ScalabilityHigh priority. We expect a high number of users concurrently accessing the applicationVerifiabilityHigh priority, as we require a high testabilityEfficiencyLow priority. The solution is not resource-intensivePortabilityLow priority. No current plan for cross platform developmentExternalAvailabilityHigh priority. Especially important during peak hours, which we expect to have from 7am to 9am, 12pm to 1pm and 5pm to 10pm.PerformanceMedium priority. The system will not require any complicated algorithms or calculations.ReliabilityHigh priority, as this would help to increase availability. Also might be perceived as "branding" requirement.RobustnessHigh priority. The system should be tolerant to users' mistakes. This also might be perceived as "branding" requirementSafetyLow priority, this system is not safety-criticalSecurityHigh priority, if we include the feature "submit loan application" (which will imply
SRE Assignment 3Page 4dealing with sensitive user data). Otherwise, low priority. In this analysis, we assume that this feature will not be a part of the application.UsabilityHigh priority, as the system will be developed to attract more customersInteroperabilityLow priority, as this is a stand-alone systemInstallabilityLow priority, as the user will not install anything. Web application.IntegrityMedium priority, if we include the feature "submit loan application". Otherwise, low priority.USE 1: a user who is unaware of the location of the store in the iMega can easily find the store.USE 2: the user can manage their account as well as they can also add their products wish lists and they can buy the products later according to the wish list.AVL 1: a huge variety of products is on sale in the same time as they have 100 retailers approximately.AVL 2: the iMega store shall be open throughout the week. And the mall should work approximately 14hours a day.AVL 3: the iMega shall provide feedback to the every user that buys a product from the supermarket.
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents