Team MasonPFDA Contextual Architecture

Oliver RettigTeam LeaderProcess ManagerPlanning Manager

Lazar CrawfordDesign ManagerImplementation ManagerCustomer Interface Manager

David HartyTest ManagerQuality ManagerSupport Manager

Primary System Functionality

Project Creation/Saving Diagram Creation/Verification Diagram Printing XML Exportation Multiple User Access

Printer

User InputDevice

User OutputDevice

NetworkPFDA

WorkstationWorkstation

Workstation

PFDA Context Diagram

Organizational FactorsOrganizational Factor Flexibility and Changeability Impact

O1: Management

O1.1: Conflicting Goals

MSE 530 and 610 have goals and intentions that do not always coincide

Communication may bridge different approaches

Moderate impact on schedule

O1.2: Aggressive Schedule

Schedule is constrained by course objectives

This factor is not flexible Large impact on schedule and completeness of design

O1.3: Requirements Volatility

The working SRSs are still under construction

Eventually the SRSs will be finalized Moderate impact on schedule and design

O1.4: Conflicting Requirements

There are currently 4 different working SRSs

Eventually the SRSs will be merged, or one will chosen as the master

Moderate impact on schedule and design

O2: Staff Skills

O2.1: Familiarity With Domain

Team has little or no experience with Problem Frames

Training can be arranged Moderate impact on schedule

Technological FactorsTechnological Factor Flexibility and Changeability Impact

T1: General-Purpose Hardware

T1.1: Computing Hardware

PFDA shall run on a standard PC-based system

As technology advances, the PC hardware platform will be upgraded

Moderate impact on design so that hardware changes are transparent

T2: Supporting Software

T2.1: Operating System

The PFDA shall support multiple Windows versions, including 98 and NT which run on different kernels

If potentially flexible Moderate impact on design to support different OS environments

Product Factors:Functional Features

Product Factor Flexibility and Changeability Impact

P1: Functional Features

P1.1: Concurrent, multiple user access

PFDA supports multiple users accessing a project

Requirement is not flexible Large impact design

P1.2: Problem Frame Diagramming

User shall be able to create, edit, save Problem Frame Diagrams

Requirement is not flexible Large impact on design

P1.3: Problem Frame Modeling & Verification

PFDA shall verify that model units are used in accordance with standard Problem Frame guidelines.

This is flexible Moderate impact on design

P1.4: XML Generation

PFDA shall be able to output Problem Frame diagrams in XML format

Somewhat flexible Light impact on design

Product Factor Flexibility and Changeability Impact

P2: User Interface

P2.1: GUI Components

The GUI shall have a menu bar, project hierarchy window, drawing window, diagram canvas window, and a status bar.

Specific arrangement and content of the GUI is flexible

Light impact on design

P3: Error Handling & Recovery

P3.1: Automatic Project Backup

When the PFDA experiences an unrecoverable error, current working files shall be available for recovery upon restart

This is a flexible requirement in terms of degree of recoverability

Moderate impact on design

Product Factors:User Interface, Error Handling & Recovery

Issue TablesIssue Influencing Factors Applicable Strategy

Requirements O1.1,O1.3,O1.4 Modularization of functional elements

Continual communications with requirements team

Schedule O1.2,O2.1 Modular design will support parallel tasking among the team

Problem Frames O2.1,P1.2,P1.3 Partition the system such that Problem Frame logic is encapsulated in distinct elements

Concurrent Multiple User Access P1.1 Apply separation of concerns along the lines of user interaction with the system and the systems primary logic

Identify an architectural style, or hybrid of styles, that will provide an interface for remote access to the PFDA

Implement a data model that enables version control for shared projects

Conceptual Diagrams: Level 1

PFDAXML

Output

userOutput

UserInput

PrinterSpool

1 1...*Server Network Client

Level 2:PFDA->Client

:shared data

:CVS

network

PrinterSpool

User I/ORequest

:Problem Frames :I/O

XML

data

datadata

UPFIUCOUCI UPFO

:Client

Level 3: PFDA->Client-> ProblemFrames

:Problem Frames

:Drawing

usermodelling in

userdrawing

in

Modelling shareddata

shareddata

userdrawing

iout

usermodelling out

Level 3: PFDA->Client-> ProblemFrames->Drawing

:DrawAcquisitionuser Draw In

userDraw Out

shareddata

:Verification:Draw

Updatedata

shareddata

data

Level 2: PFDA->Server:server

data store

:user verification:Project

Management

network

communication

dat

a

dat

a

datadata