click below
click below
Normal Size Small Size show me how
MCPD - 70-547 - Ch 1
Designing and Developing Web-based Applications
| Question | Answer |
|---|---|
| use case | describes a set of tasks a user peforms to get work done |
| requirement | defines the scope of the application |
| QOS requirements | "defines contractual, non-functional requirements for a system, i.e. performance, load, availability, stress, accessibility, and maintainability" |
| User requirements | scenarios; high-level scenarios |
| Functional specifications | "definitions of functions, operations, and interfaces" |
| Business requirements | defines the high-level goals of the project; there are no detailed specifications at this point |
| Step 1. Requirements Evaluation | "Are the requirements - business,qos, user, functional - complete?" |
| Step 2. Requirements Evaluation | Are the requirements unambiguous? |
| Step 3. Requirements Evaluation | Are all the requirements necessary? |
| Step 4. Requirements Evaluation | Are all the requirements feasible? |
| Step 5. Technology Evaluation | "What type of client? Standard browser, ajax, smart, office, mobile" |
| Step 6. Technology Evaluation | Any third party controls? |
| Step 7. Technology Evaluation | What type of application server? |
| Step 8. Technology Evaluation | What type of application libraries? |
| Step 9. Technology Evaluation | What type of security? |
| Step 10. Technology Evaluation | "What type of data storage? File, SQL Server,SQl Express, SQL Everywhere, Oracle?" |
| Step 11. Existing Asset Investigation | Are there already existing solutions for this problem? |
| Step 12. Create High Level Design | Create overall application architecture |
| good requirement | "unambiguous, measurable, actionable" |
| Step 13. Create Prototype | |
| Step 1. Prototyping | Create html screens with dummy data and fake navigation |
| Step 2. Prototyping | Confirm client-side experience |
| Step 3. Prototyping | "Confirm application container, framework, master pages, design, styles, etc." |
| Step 4. Prototyping | Define user interface elements |
| Step 5. Prototyping | Evaluate web services requirements |
| Step 6. Prototyping | Evaluate security model |
| Step 7. Prototyping | Evaluate third-party controls |
| Step 8. Prototyping | Evaluate data access and storage methods |
| Step 9. Prototyping | Evaluate state management |
| Step 10. Prototyping | Identify missing requirements |
| Step 11. Prototyping | Identify design challenges |
| Step 12. Prototyping | Create estimate |
| Principal Goal of Requirements Phase | Reach a common understanding among developers , business, and users |