Busy. Please wait.
or

show password
Forgot Password?

Don't have an account?  Sign up 
or

Username is available taken
show password

why


Make sure to remember your password. If you forget it there is no way for StudyStack to send you a reset link. You would need to create a new account.
We do not share your email address with others. It is only used to allow you to reset your password. For details read our Privacy Policy and Terms of Service.


Already a StudyStack user? Log In

Reset Password
Enter the associated with your account, and we'll email you a link to reset your password.
Don't know
Know
remaining cards
Save
0:01
To flip the current card, click it or press the Spacebar key.  To move the current card to one of the three colored boxes, click on the box.  You may also press the UP ARROW key to move the card to the "Know" box, the DOWN ARROW key to move the card to the "Don't know" box, or the RIGHT ARROW key to move the card to the Remaining box.  You may also click on the card displayed in any of the three boxes to bring that card back to the center.

Pass complete!

"Know" box contains:
Time elapsed:
Retries:
restart all cards
share
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

  Normal Size     Small Size show me how

MCPD - 70-547 - Ch 1

Designing and Developing Web-based Applications

QuestionAnswer
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
Created by: jhlee5