CMIS 270 Exam 3
Agile Manifesto
*Individuals and interactions* over processes and tools *Working software* over comprehensive documentation *Customer collaboration* over contract negotiation *Responding to change* over following a plan +++That is, while there is value in the items on the right, we value the items on the left more.
Database Approach
*Positives* Minimal data redundancy Consistent data Integration of data Sharing of data Data independence Ease of application development Reduced program maintenance
3 levels of Planning in Agile
1. 4 releases per year - each release is 10 weeks 2. 2-week sprint (about how far we can plan in advance) 3. Daily Stand-Up Meeting
3 levels of planning in Agile
BPUF: Big planning up front - don't worry about what will happen 8 months from now. 1. 4 releases per year - each release is 10 weeks 2. 2-week sprint (about how far we can plan in advance) 3. We'll get to in a bit.
Guidelines for Controlling Data Input
1. Class or composition 2. Combination controls 3. Expected value/Reasonableness controls/Range controls 4. Completeness controls (missing data) 5. Pictures/templates
Rinse and Repeat (SCRUM/Agile)
An iteration is a cycle of work In SCRUM, we call this a sprint. Typically 2-week sprints (10 days). But you may see larger.
Natural Language Interaction
Handwriting Recognition Voice Recognition
User Stories
In old days was written on 3x5 index card (now it's electronic). Keep the 3Cs in mind: Card, Conversation, Confirmation AND, keep RGB in mind: Role, Goal, Benefit
Planning Poker
Key facts: ROUGH estimate FAST not precise FtF - 4 people Steps: 1. Read something you need to estimate 2. Everyone comes up with their own number 3. All reveal your numbers 4. Discussion (2 minutes) - high/low votes 5. Revote
Step 6 Agile: Demo
Last day of sprint, meet with customer to demo what has been accomplished.
Important things to consider about input of data...
Missing class notes
Input Design: Common interacting devices
Missing class notes
Step 4: Estimate and Plan
Now we have priority, but how do we know how much will fit in a release? Remember WAG and SWAG? Planning Poker
Step 5 Agile: DO
Pair programming: checking code as we write, removes 1/2 defects. Test code as early as possible Test early, test often
Methods of Data input
Radio Button Check Box List Box / Drop-down List
72% of Agile flavor used is _______
SCRUM
Triple Constraints
Scope, Cost, and time. All interrelated. Can't change one without changing another.
Improving your User Story (INVEST)
Independent Negotiable (should have room for improvement) Valuable (Something a stakeholder wants/requested) Estimateable (we think we haave enough info for our planning group to estimate how much time this story will take to complete) Small (<2 weeks, or break up) Testable (do we have enough info to know when we're done?)
Planning Poker questions
What are these from? Why no big numbers? What if we have 2 votes for 1 and 2 votes for 8? Who are we thinking of when we estimate? How long should each estimation for each story take? What does each point represent?
Daily Stand-Up meeting
Team members stand to answer the following 3 questions: 1. Two things I accomplished yesterday? 2. Two things I want to get done today? 3. Are there any obstacles that might keep me from meeting my goal for today?
Data Dictionary
The repository of all data definitions for all organizational applications.
Level of Use Case
White - as seen from clouds (summary) Kite - "birds-eye view" Blue - sea-level view Fish - below sea-level Black - bottom of the sea (detail)
With SDLC the _______ is fixed - We knew what we wanted. But today, ______ is what is changed the most often.
scope We need a methodology where we can vary the scope as needed
Step 7 Agile: Retrospective
Lessons learned What worked well What didn't work What should we change Technique: Speedboat game Innovationgames.com
Mistakes to avoid (Agile)
1. Thinking you know more than you do - trying to plan too far out in the future 2. Always saying "yes" 3. No speed buffer 4. Forgetting there are 3 levels of planning
What we'll show in a DD:
Table (file) (entity) name All fields (attributes) within the table (shown as columns in the table). For each field (all of this information together makes one record - shown as a row on the table): ++Name ++Note if primary key ++Definition/description of field ++Data type (whether its numeric or character plus the length)
How much goes in a 2-week sprint? How about a release?
How much did you do last time? Oh, you never worked together before? Remember, goal is to not miss. First, a definition: Point People: how many on team (developers and testers only) How many points can we do each sprint? Remember we said about 5 points per person per week? But, things happen - so figure 7 points per person per sprint.
Step 1: Market Know your customer PIPE
•Principal: person with purse, pays for project •They may have a different set of requirements •Insider: installing, maintaining, updating system (IT people) •Partner: business partners •End Users: People who are going to get the information
Have a vision
•Should be something you can explain to a friend in an elevator •What are we doing? •Why are we doing it?
Step 3: Prioritize
++++MoSCoW ++++20/20 +++Breaks ties, good for small lists (20 or less), compares 2 things at a time ++++Buy a feature +++Market priorities, spend as a group, not enough money to get everything ++++Prune the product tree Helps you select core features, can move others sticky notes around www.innovationgames.com
Why Agile Methodology?
+++80% of new software development uses an agile method +++All about quality and speed +++SDLC requires the end user to be able to specify in detail the requirements UP FRONT!! Not always possible today. ++Trying to eliminate risk
Designing a relational database
++Create a table (file) for each entity type. ++Choose a primary key for each table. ++Choose appropriate data types and value restrictions for each field. ++Create new tables to represent many-to-many relationships. ++Add foreign keys to represent one-to-many relationships. ++Define referential integrity constraints. ++Evaluate schema quality and make necessary improvements.
What else we might show about a Field
++Data integrity +++Default values ++Picture Control ++Range controls ++Other controls as discussed last class period
Guidelines for Structuring Data Entry
++Don't enter data that already is in computer or can be calculated ++Use defaults, lists, & table lookups ++Identify units ($, dozens) ++Place captions adjacent to fields ++Provide formatting examples ++Automatically justify data entries ++Provide help ++Be consistent and adhere to standards
Creating a data dictionary
++Each entity on your ER diagram will become a table in your relational database. ++All fields in the table (or attributes on your ER diagram) will be listed.
Databases
++File Systems ++Databases ++++Hierarchical Database Model ++++Network Database Model ++++Relational Database Model** ++++++A data structure organized as a collection of tables ++++++Tables consist of rows and columns, which may be interconnected. A row corresponds to a record; columns correspond to attributes (fields) in the record. ++Object Oriented Database Model
Highlighting Guidelines
++Includes blinking, audible tones, color differences, intensity differences, size differences, font differences, boxing, underlining, ALL CAPITAL LETTERS, offsetting positions ++Use sparingly to draw user to or away from certain information (errors, warnings, keywords, high priority messages, changed data, data outside normal ranges ++Use consistently
Guidelines to Design
++Maintain consistency and standards ++Allow shortcuts and accelerator keys ++Provide feedback to user actions ++Provide logical sequencing & closure ++Report all errors & suggest solutions ++Allow for reversals of actions ++Make the user feel in control ++Provide simplicity and ease of use
Design Specifications for Forms, Reports, & Screens
++Narrative Overview +++++Who will use it? +++++What & when is the task performed? ++Sample Design ++Testing and usability assessment +++++Can you complete the task efficiently? (time to learn, speed of performance, rate of errors, rate of retention) +++++Is the form/report accurate? (expectations, confidence) +++++Do you like using the form/report? (satisfaction)
Step 2: Analysis
++Where business analysts talk to clients about what they want. *Hierarchy:* +++++*EPIC* (We we do over course of a year) ++++RELEASE (4x year) (lasts about 10 weeks in a SCRUM) +++SPRINT (4x in a release) (2 weeks in length) ++USER STORY (several in a sprint) +TASK
Text Guidelines
+Avoid large blocks of text; reading is 25% less efficient online +Limit lines of text to 60 characters +Left justify text to improve readability +Avoid words in all upper case letters +Clear and specific titles describing content and use +No hyphens, abbreviations, or acronyms +Revision date or date when data was generated
Color Guidelines
+Only useful when information is most effectively displayed (cannot improve on garbage) +Limit browser-safe colors to 3 or 4 complimentary colors +Simplify background +Can be soothing, provide interest, emphasize logical organization, and draw attention to warnings +Can degrade resolution and fidelity with different display units and can be a problem for color blindness
Navigation Guidelines
1. Use consistent means of navigation with visual cues. 2. Include a navigation bar if needed 3. Provide a site map 4. Place illustrations near text. 5. Allow for shortcut keys
Layout Guidelines
1. Create a unique site identity and *strive for consistency* -Fonts -What is background, foreground -Graphics size, color, shape 2.Natural Eye movement 3. White space 4. Margins 5. Grids
Guidelines to controlling user access
1. Identify users with authentication schemes Passwords & user Ids Biometric devices (finger prints, signatures, retina prints, voice prints...) 2. System access control -Missing class notes 3. Authorization rules -Missing class notes
How is it different from SDLC?
Do things in 2 week periods called sprints Spend first day planning what needs to be done Next 8 days spent doing i Last day spent demoing (done by business analyst)
General Guidelines Categories
Layout Text Color Highlighting Navigation