Prototyping Model : Software Engineering

-

  • stakeholders better understand what is to be built when the requirements are fuzzy.
    • eg. fitness app sync user interface screens, social integration, fitness goals and share progress requirements
  • quick planning of prototyping iteration.
  • modelling (quick design)-focus on parts visible to end users.
  • evaluation of stake holders- to satisfy various needs and better understand what needs to be done.
  • users get to feel actual system and developers get to build something quickly.
Limitations:
  • developers may need to discard a prototype to meet the customers' evolving needs.
  • if not careful, less than ideal choices become the integral part of the evolving system.
  • customers involvement may cause delays.

Comments

Post a Comment

Popular posts from this blog

Database Normalization : 1NF, 2NF, 3NF, BCNF, 4NF

-
Image
What is normalization? Breaking down a table into functionally independent tables Follows three-step procedures {first normal form, second NF, third NF} Why normalization? Reduce data redundancy, and thus data anomalies 1NF All the key attributes are defined There are no repeating groups in the table All attributes are dependent on the primary key 2NF It is in 1NF It includes no partial dependencies Partial dependency : attributes are dependent on only a part of a composite PK Fig: Dependency Diagram 3NF It is in 2NF It includes no transitive dependencies Transitive dependency : nonkey (nonprime) attributes are dependent on another nonkey attribute BCNF A Table is in BCNF when it is in 3NF and contains no non-key attribute that determines a key attribute. – Convert to BCNF by exchanging the determinate with the key attribute and then resolving the partial dependency with a new table. 4NF A Table is in 4NF when it is in 3NF table with no multi-valued dependencies :  – Convert to 4NF
Read more