The Autobots/Milestone1
From Software Engineering
Contents |
[edit] Use Case 0 – Create Builder Account
Primary Actor: Admin
Stakeholders: Builder, Site Admin
Precondition: Admin has Builder's information
Main Success Scenario
1. Admin logs in
2. Admin selects to add builder
3. Admin enters builder information
4. Information is entered into database
5. Builder account is created
Extensions:
1a: Admin has unsuccessful login.
- 1a.1: Admin asked to re-enter information.
2a: Builder's information is not valid.
- 2a.1: Admin receives error message and asked to re-enter information.
4a: Builder already exists.
- 4a.1: Admin receives error message.
[edit] Use Case 1 – User Logs In
Primary Actor: User
Stakeholders: User, Site Admin
Precondition: User Account has been created and using valid password
Main Success Scenario
1. User accesses HomePix homepage
2. User enters username and password into fields
3. User submits username and password
4. User is directed to their personal HomePix page
Extensions:
3a. User entered invalid information.
- 3a.1: User is prompted to try again.
[edit] Basic Architectual Decisions
1. Platform
We are using the .NET framework for this project because of the communication required between the program and the database that needs to be accessed.
2. Programming Language
We are using C# to create the web page for the client. C# is being used at the request of the client.
3. User Interface
The user interface for our program is a graphical web page. It will be a simple design and easy to use. A web page is used because the project is required to be on the internet.
4. Persistence Mechanism
We are using a SQL database to store all persistent data. This is used at the request of the client.
5. Most Important Libraries
C# System Web Libraries are the most important libraries we are using. This is because we are creating a website that requires the security and communication functions that these libraries provide.
[edit] Basic Infrastructure
1.Web site set up
The website is set up so that there is a login box on the main page where all users will log in. If the user that logs in has admin permissions, then the user will be redirected to the admin page where all admin functions can be performed. If the user that logs in is a builder, the user will be redirected to their specific builder page where they can perform functions specific to their company. If the user that logs in is a consumer they will be redirected to their personal page. If the user that logs in is a guest they will be redirected to the specific photo page that they have permission to view.
2.Database set up
The database we are using has multiple tables. There is a table that contains the information for the builders and the users for general login. This table will contain all the users information. There will be another table for Builders which contains their information.
3.IDE set up
We are using Microsoft Visual Studio to develop our project. This helps our productivity because of the GUI builder, automatic highlighting and drop down lists with variable and function names lessen the amount of work that needs to be done by hand.
[edit] Introduction to the Requirements Document
1.Purpose and Scope
The purpose of our requirements document is to outline the functionality and limitations of our project. It provides a mockup of what the finished product might look like and provides an outline of what the finished product will do.
2.Glossary
The terms used in our requirements document are mostly common computer terms. No technical glossary is necessary at this point in time.
3.Nonfunctional Requirements
Some of our nonfunctional requirements are the security features that must be provided to ensure that personal information is not compromised. Our code should be fairly simple which in theory will make it fast, reliable, and easily maintained. Our final product will be commented so that future maintainers will know what features are provided for and what specific functions perform.
[edit] Proposed Use Cases for Milestone Two
2.Admin Views List of Current Builders
3.Admin Prints List of Current Builders
4.Create Consumer Account
5.Consumer Changes Personal Information
6.Builder Changes Personal Information
7.Builder Deletes Consumer Account
8.Admin Deletes Builder Account
9.Builder Views List of Current Consumers
10.Builder Prints List of Current Consumers
11.Admin Views Billing Information for Current Builders
