Requirements Modeling

Modeling is how one would represent the system design.

The steps required in representing a system design are
similar to those of an artist beginning a new painting. The
initial sketch on the canvas has rough edges and lines that
are not precise. Once the initial sketch is complete, the
artist’s vision becomes clear. This rough-draft process
parallels the requirements modeling process. Details are
not figured out yet, but there is enough information to
make the system vision clear. In requirements modeling,
the systems analyst is performing the equivalent of an
artist’s rough sketch. The rough estimate and model
provide enough vision and information to determine the
feasibility of the project. The feasibility determines about
how much it will cost, about how long it will take, generally
what type of resources are needed, and a high level
architecture to determine how it can it be done.
Collectively, this information drives the project feasibility to
answer the questions of should the project be done, can
the project be done, and when the project should be done.

A high level modeling example for the previously

discussed project request can be seen below. The request
was to develop a report in order to show department sales
growth:

• This project should take 2 calendar months and will

need 1 calendar month of 1 data developer and 1
 report developer’s time to create the project
deliverable. The project will need 2 calendar months
of the systems analyst’s time to plan, design, model,
verify, implement, and support the project.
• The total project cost should be under $30,000: 2
resources at $30/h x 1 month (4 weeks x 40h)
=$9,600 and one resource at $50/h x 2 months (8
weeks x 40h) = $16,000 to $25,600. Rounding puts
the project at $30,000. Typically an estimate is
considered reasonable if the estimate falls 10% above
or below this high level number.
• A data flow diagram will show data coming from a
transactional source database that has the sales line
items. The data will go through an extract, translate,
and load (ETL) process, which will store data into a
SQL Server-reporting database. The report will be
generated using Microsoft SharePoint Business
Intelligence web parts where users will interact with
the database itself.
• Report sample layouts and working prototypes
provide additional requirements modeling options for
the user to review and interact with. The sample
layouts can put a visual presentation in front of the
user who can then provide direct feedback regarding
usability. A working prototype in SharePoint is a rapid
requirement modeling method to provide mock data
and a sample version of a working report. The rapid
requirement modeling method provides a deeper user
 experience in the model step to further define the
requirements of use.
It is important to note that, in practice, most modeling at
this phase begins on a whiteboard or even on a napkin at
a lunch meeting. Modeling is intended for a systems
analyst to bring a user idea to life.

In Module Four, students will continue to explore the

concepts that detail performing logical data models. Data
modeling will occur when students begin to construct the
data flow diagrams and build the relational data model to
store and access data for the system.