Welcome to Lewis's site

Things I'm working on and interested in....
Home
About Me
IT Arch Stuff
Music
Food
Contact Me
Site Map
PBA Zone : Requirements Environment : Functional Requirements Area
 
Functional Requirements Area

Functional requirements are crucial for any architect to understand when designing a solution.  There are many ways to document functional requirements today.  Examples include the Unified Modeling Language (UML) + many more.   No one documentation standard is considered "complete."
 
 
Perspective Capture Questions:
 
Whom will interact with this solution (people, systems, etc...) ?
 
How will these people and/or systems interact with this solution?
 
What do these people and/or systems functionally observerably expect from the solution?
 
Why do they want or need these specific functionality observable behavior delivered?
 
How will these functional expectations evolve over time?
 
What is the expected functional lifespan of this solution?

Alternative Impact Questions
 
How will alternative architecture decisions impact whom will intereact with this solution? (people, systems, etc...)
 
How will alternative architecture decisions impact how these people and/or systems intereact with this solution?
 
How will alternative architecture decisions impact what these people and/or systems functionally observerably expect from the solution?
 
How will alternative architecture decisions impact the motiviation for the specific functionally observable behavior delivered?
 
How will alternative architecture decisions impact how these functional expectations evolve over time?
 
How will alternative architecture decisions impact the expected functional lifespan of this solution?
Proposed Solution Impact Questions
 
How will proposed architecture decisions impact whom will interact with this solution (people, systems, etc...)?
 
How will alternative architecture decisions impact how these people and/or systems intereact with this solution?
 
How will proposed architecture decisions impact what these people and/or systems functionally oberverably expect from the solution?
 
How will proposed architecture decisions impact the motivation fo rthe specific functionality observable behavior delivered?
 
How will proposed architecture decisions impact how these functional expectations evolve over time?
 
How will proposed architecture decisions impact the expected functional lifespan of this solution?