9.4 Capstone Project - Milestones #1, #2, and #3 - Haynes - CIS613
docx
keyboard_arrow_up
School
Bellevue University *
*We aren’t endorsed by this school
Course
613
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
7
Uploaded by BarristerKudu2862
Milestone #1 (75 points) – Progress Check Only: Week #7, Day 7:
Industry: Textiles, Upholstery, Fibers and Fabrics, Arts & Crafts
Company Name: BJ’s Buttons, Fabrics & Crafts
Items Sold: Buttons, Yarns, Threads, Fabrics, Patterns, Sewing Machines, Arts & Crafts, Beads, Baskets
1. Identify the following information about the application:
a. Purpose or goal of the system. Please make this at least a paragraph.
The purpose of the system is to make it easier to search for a particular item and have the items accurately displayed. This will also display whether the item is available. It will allow the users to manage their cart and be able to see the total item count. The system will make it easy to search for the item and make purchases. The user will have the ability to pick up the items in store or have it delivered direct to them. b. Primary user(s) of the system. This must include all users that will be referenced in your work and must also include a description of each user. Every user you use anywhere else in this project
must be defined here!
Customers – the people who make purchases from the company.
Employees – the people who work for the company.
Payment Processor – the company that processes the payments.
2. Generate an Activity UML diagram that starts with the customer connecting with the web site and ends with the order available for pickup or ready for delivery. This should be a very focused and specific UML Activity diagram.
3. Using the activity diagram created for step 2, generate 15 User stories, each with 2 acceptance criteria (30 acceptance criteria total). See assignment 3.4 for details.
4. Convert the User stories from step 3 into User Requirements. Convert the acceptance criteria into System Requirements.
5. Produce a Use Case UML diagram that contains a minimum of the Customer and the Worker. Review the User stories from step 3 for ideas as to the features to include in the Use Case diagram, but all features need not be included.
User Story
User Requirements Acceptance Criteria
Sprit
1.
As a customer, I want to make a purchase. 1.
The system shall
require the customer to have a registered
account or make
one in order to make a purchase. To make a purchase a registered account is needed. If the user does not have a registered account, one can be created. 1
2.
As a customer a username and password are required to log into an account. 2.
The system shall
verify a valid username and password to login. A valid username and password to login into the system.
1
3.
As a customer who has forgotten their password, I need
3.
The system shall
request the student to provide the The password has been forgotten or account has not been
used in a while. The 1
to complete a password reset so I can access my account. identifying information before a password reset link can be sent.
password rest button is located on the login screen below password box.
4.
As a customer who has successfully login, the main dashboard of the
website will be displayed.
4.
The system shall
display the main
dashboard of the
webpage. It will display the company name and logo clearly.
1
5.
As a customer, I will utilize the search bar to find the item I need.
5.
The system shall
search for the items or words placed in the search bar. To find a specific item the search will be utilized. It will search for the words or specific items typed in the search bar. If the item is not
available display item note found. 1
6.
As a customer, I will be able to see the item and information displayed when clicked on. 6.
The system shall
display the item name, description, price, and product type. The item name and price will be displayed.
The description will be presented clearly. The product type will be displayed. 2
7.
As a customer I should be able to see the images that go along with the item, 7.
The system shall
display the images that go along with the item. The image should be
displayed clearly. The image should be
linked directly to the item. 2
8.
As a customer I will be able to see the total count of items in
the cart.
8.
The system shall
display the item count accurately
as items are added or removed. Items should be displayed in the cart along with the total item count. 2
9.
As a customer I will have the ability to manage their 9.
The system shall
allow items to be added and deleted. Prior to entering checkout, the cart can be managed.
The customer can 2
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
cart. add and remove items. 10. As a customer I will check the availability of the item, so I can add it to the cart.
10. The system shall
display the availability of the time and update as items are purchased. If the item is available, then it will
have the ability to be
added to the cart.
If the item is unavailable, then the display item is out of
stock and will not have the ability to be
added to the cart. 2
6. Using the system requirements from step 4, produce 10 system test cases. (See assignment 7.3).
Test Case #1 – Active Customer Account
Valid if the customer has a registered account.
If yes, test login functionality
If not, test the process to create an account.
Test Case #2 - User Verification
Test for valid username
Test for valid password
Test Case #3 - Account/Password Recovery
Test the forgot password functionality.
Test the functionality of the password reset.
Test Case #4 – Login
Verify the login screen is displayed.
Test functionality of logging in with username and password.
Verify that the main dashboard will display after successful login.
Verify logo and business are displayed clearly.
Test Case #5 – Search bar
Test functionality of the search bar.
Verify the right items are pulling from search.
If an item is not available, verify that no items found are displayed.
Test Case #6 – Item Display
Verify the correct Item name is displayed.
Verify the correct item description is displayed.
Verify the correct price is displayed with the correct item.
Verify the item is displayed in the correct product type.
Test Case #7 – Images
Test functionality of images are being displayed properly.
Verify that the images are clearly displayed.
Verify the correct images are being displayed for item.
Test Case #8 – Cart Count
Test the functionality of cart count.
Verify the cart count is being displayed correctly and total items are accurate.
Test Case #9 – Editing the Cart
Test the functionality of adding an item to the cart.
Test the functionality of removing an item from the cart.
Test Case #10 – item availability
Display the availability of the item.
Verify that the customer cannot add more then what is in stock.
If the item is out of stock, verify that the item cannot be added to the cart.
7. Identify whether a plan-driven "waterfall" software development approach or an agile framework or methodology might be more suitable for this software development project. Explain your recommendation.
An agile framework would work the best in this industry. This allows retailers to keep up with the changing conditions in the market and technology. This methodology allows the retailer to keep up with the change in demand and address the need for faster delivery, as well as integration. This gives the retailer a chance to remain competitive by moving fast and experimenting with directions which help promote innovation. While the waterfall method requires the phase to be completed before moving on to the next and cannot handle systems that are rapidly changing. 8. Identify at least five evolution or maintenance related items that should be considered when planning to develop the software application.
Preventive maintenance should be considered when developing the software application. Preventive maintenance will look to the future and ensure the system will continue to work as it was intended. This can include but is not limited to making necessary changes, upgrades, adaptations, etc. Perfective software maintenance is important to keep in mind as well. This will aim to adjust the software by adding new features that are necessary and removing ineffective features or that are no longer relevant.
Another one to keep in mind is Adaptive software maintenance. This will allow the software to adapt to the changes that are made in the system to properly meet new requirements and continue
running as intended. This is required when dealing with changes in technology to keep up with the rules and policies regarding the software. Corrective software maintenance is another necessity. This type of maintenance is required when
something goes wrong with a piece of software. This could include faults and errors, which could
impact the functionality of the software and would need to be addressed quickly. Furthermore, growth in the user base needs to be considered. If this is addressed early on then it will not affect the performance and reliability. 9. Identify ten or more SOFTWARE DEVELOPMENT risks that could develop with this project.
What is the probability or likelihood that each risk might occur, and what would be the effect to your application if it did? What is your plan to avoid, minimize or recover from (i.e., contingency plan) each of these risks if they were to occur? Present your risk analysis as a Risk Register in a tabular format, with the highest impacts/effects listed first. A brief sentence is sufficient to describe a risk mitigation strategy.
Risks
Probability
Coding issues
Low
Integration issues
Low
Inventory accuracy Low Scope Variation risks
Low
Unmet Expectations Medium
Performance risks
Medium
Market risk Low
Technical issues Low
End –user engagement risks
Low
Inaccurate Estimation risks
Low
The best way to handle risk management is to incorporate it into the plan and include risk mitigation.
This will include identifying the risks, performing a risk assessment, prioritize, track the risks, implement
and monitor the progress.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Reference:
Sommerville, I. (2016). Software Engineering (10th Edition, p. 159 -161) Pearson.