Last Updated: 2/11/2017

Teams will be given a business problem statement to analyze and design. Any widely used methodology may be used such as Object Oriented Analysis, Structured Analysis, Information Engineering, Prototyping, etc. The business model does not have to be fully implemented; however, a system design that allows user prototyping with screen/window/web page interaction will be considered in the over-all grading.  This contest is software and methodology independent.

Team Composition

Your team may be made up of 1-2 students.


This contest will take place on Thursday, April 6, 2017 from 6:30 PM – 10:30 PM


The problem statement will allow multiple analysis and design methodologies, which may include:

  • Structured analysis
  • Object-oriented analysis
  • Information engineering
  • Rapid application design and prototyping
  • Any other widely accepted methodology

NOTE: Competitors are expected to utilize ONE and ONLY ONE Analysis and Design approach.  Using a combination of components from both the Structured/Information Engineering approach and the Object Oriented approach should be avoided.


Teams must provide own business modeling software. This could include any CASE, I-CASE or other model-based development product. Example tools may include: Oracle Designer/Developer, Unified Modeling Language, Visible Analyst, CA Cool Gen, Cool Jex, etc.

Solutions should be submitted as Microsoft Word or PDF files.


Teams will be given the problem statement at the beginning of the contest time.  Time will be allowed to read the problem statement and ask any questions in a common session.  Once the question & answer time has closed, no further questions will be answered.  At the end of the contest period, each team will be asked to either copy their solution for judging.

  % Structured/Info. Engineering Object-Oriented Approach
Information Flow 40 Decomposition, DFD’s, Dependency and Process Action Diagrams. Use Case Diagrams, Use Case Descriptions, Sequence and/or Activity Diagrams
Information Structure 40 Entity Relationship Diagrams (ERD’s) and Data Constraints Class Diagrams (for objects in persistence storage)  and State Charts (State Machine Diagrams)
Prototyping 20 Windows, Screens and/or Web Pages Windows, Screens and/or Web Pages
Overall 100    

Note: The Prototype does not have to execute on a computer. The prototype may be prepared using any number of software packages including as examples (Word, Paint, Access, Visual Studio, Photoshop, just to name a few). Make sure you arrange the interface screens in a hierarchical or logical successive order that represents a user dialog with the interface screen. Sample data should be included on the interface screen. In other words, more points will be given for a prototype that appears to be working for a given transaction/test scenario (appears to be a real dialog).

Past Problem Statements

Leave a Reply

Your email address will not be published. Required fields are marked *