Presentation is loading. Please wait.

Presentation is loading. Please wait.

Initial Requirements and Design. Second stage of development Requirements Document Design Document Quality Assurance(QA)

Similar presentations


Presentation on theme: "Initial Requirements and Design. Second stage of development Requirements Document Design Document Quality Assurance(QA)"— Presentation transcript:

1 Initial Requirements and Design

2 Second stage of development Requirements Document Design Document Quality Assurance(QA)

3 Our product appeals to almost every demographic. Jenny Bits, an elementary school student Phyllis Lin, University Student Tim Bucks, teaching assistant at SFU James Power, 39 year old computer technician Linda Bytes, 71 year old Grandmother Who its not for, people without computers. No, our software will not run on cell phones.

4 Tim Phyllis

5 Special Attention given to optimization Boot up in less than 8 seconds Full program sized less than 20mb. Between 10 and 30MB of ram used at any one time (Pentium 4 with 1GHz processor and 512MB ram or higher assumed) Reliable, Robust and can run on Windows and Macintosh. Usernames and passwords all secured

6 Full user tutorials on basic functionality. Screenshots included of GUIs first version.

7 We all try to use the same programs and the same version of those programs Java 5 Eclipse IDE 3.4.x SQLite Smack etc… Respect Ethics and the Law

8

9 Using SQLite for storing this information User profiles Chat log All other local data. Simplifies data storage by allowing us to use one database file (profiles.db) to save all information.

10 Blueprint of which features will be implemented in each version. Example: Chatbot Implementation Details Non-essential for basic chatting. Release in alpha to experience 3 phases of user testing. Requires new windows created in GUI. Saves configuration data to database. Uses core to determine whether to auto-reply.

11 Three main stages of testing Unit testing Integration testing User acceptance testing

12 Junit is used for unit testing: Unit Testing: individual testing of each class and method. Both black-box and white-box test cases. Sample test public void testUserStatusChange { UserProfile userProfile = new UserProfile(); userProfile.setStatusMessage("This is a test!"); assertTrue(!userProfile.getStatusMessage().isEmpty()); userProfile.clearStatusMessage(); assertTrue(userProfile.getStatusMessage().isEmpty()); }

13 After unit testing Incrementally add components: core, database, GUI Use fully automated tests to ensure compatibility Why: Parts of the program may work perfectly alone, but may not interface with each other well.

14 Create focus groups of external users to try programreport back on bugs and features they would like added. Approximately 20 users, test different things: Adding friends Chatting Menu options Why is it important? Three stages, so that design changes can be incorporated into later revisions; not the upcoming release.

15 Google Calendar The entire team can see this and it keeps us organized 40% of days are allocated for testing.

16 How do we know which are the most important areas to focus testing on? Estimation:

17 Thank you for listening to our presentation. For more information, please visit: May we answer any questions?


Download ppt "Initial Requirements and Design. Second stage of development Requirements Document Design Document Quality Assurance(QA)"

Similar presentations


Ads by Google