EVALUATION OF AXIOMATIC DESIGN FOR DESIGN REUSE By Laura J. Aguilar A MASTER OF ...

86 Pages·2007·2.45 MB·English

by  Deb Metzger

System Engineering Requirements for the Professional Development Interface (PDI)
By
Debra L. Metzger
A MASTER OF ENGINEERING REPORT
Submitted to the College of Engineering at
Texas Tech University in
Partial Fulfillment of
The Requirements of the
Degree of

MASTER OF ENGINEERING
Approved

______________________________________________
Dr. A. Ertas

______________________________________________
Dr. T. T. Maxwell

______________________________________________
Dr. M. Tanik

______________________________________________
Dr. J. Woldstad

October 27, 2007
ACKNOWLEDGEMENTS

This paper would never have been written if it were not for the Raytheon Leadership – Bill
Swanson, Raytheon Chairman and CEO and Mike Keebaugh, Intelligence and Information Systems
President – who make possible the education and training benefits that fund Texas Tech University’s
Master of Engineering program.
I would also like to thank Mike Hanavan and Marcia Davis for their steadfast support and
encouragement, and especially for putting up with my testy moods on Mondays after I spent long
weekends on school work. I could not have done it without you both. Thank you.
A special “shout-out” to my friend, Kris Crocker for editing my papers and ensuring I sound
intelligent.

ii

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
TABLE OF CONTENTS
DISCLAMER....................................................................................................................v
ABSTRACT...................................................................................................................................vi
LIST OF FIGURES..........................................................................................................ix
LIST OF TABLES...........................................................................................................ixi
CHAPTER I INTRODUCTION........................................................................................1
1.1 Scope............................................................................................................................1
1.2. Approach......................................................................................................................1
1.3. Boundaries...................................................................................................................3
1.4 Expectations..................................................................................................................3
CHAPTER II BACKGROUND.........................................................................................7
2.1 Origination....................................................................................................................7
2.2 In Existence...................................................................................................................8
CHAPTER III CONTECTUAL ARCHITECTING............................................................9
3.1. Contextual Architecting.................................................................................................9
3.2 Scope..........................................................................................................................................9
3.2.1 Goals, Stakeholders/Viewpoints...........................................................................................10
3.2.2 Key Scenarios...........................................................................................................11
3.2.2 Quality Attributes......................................................................................................12
3.2.3 Context Diagram.......................................................................................................14
CHAPTER IV OPERATIONAL ARCHITECTING........................................................16
4.1 Concept.......................................................................................................................16
4.2 Use Cases....................................................................................................................18
4.3 Activity Diagram.........................................................................................................22
iii

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
CHAPTER V LOGICAL ARCHITECTING....................................................................25
5.1 Architecture Trade.......................................................................................................25
5.2 Domain and Class Collaboration....................................................................................28
5.3 State Charts.................................................................................................................32
5.4 Sequence Diagram.......................................................................................................33
CHAPTER VI PHYSICAL ARCHITECTING.................................................................35
6.1 Design Trade-Offs........................................................................................................35
6.2 Block Diagram.............................................................................................................35
6.3 Data Class Diagram......................................................................................................38
6.4 Data Schema................................................................................................................40
6.5 Interface Definition......................................................................................................42
CHAPTER VII REQUIREMENTS..................................................................................47
7.1 Requirements...............................................................................................................47
7.2 Requirements Identification..........................................................................................47
CHAPTER VIII CUSTOMER REQUIREMENTS...........................................................49
8.1 Overview....................................................................................................................49
8.2 Customer Requirements (CR)........................................................................................50
CHAPTER IX FUNCTIONAL REQUIREMENTS..........................................................51
9.1 Overview....................................................................................................................51
9.3 Functional Requirement (FR)........................................................................................51
CHAPTER X DERIVED REQUIREMENTS...................................................................56
10.1 Overview...................................................................................................................56
REFERENCES................................................................................................................70
APPENDIX A COTS PRODUCTS...................................................................................72
iv

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
DISCLAMER

The opinions expressed in this report are strictly those of the author and are not necessarily those
of Raytheon, Texas Tech University, or any U.S Government department or agency.
This document discloses subject matter in which Raytheon Company has proprietary rights.
Neither receipt nor possession thereof confers or transfers any right to reproduce or disclose the
document, any part thereof, any information contained therein or any physical article or device, or to
practice any method of or process, except by written permission from, or written agreement with,
Raytheon Company.

v

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
ABSTRACT

This paper is in fulfillment of an Individual Final Assignment, a requirement of the Texas Tech
University Systems Engineering Master’s Program.
Currently within Raytheon’s Intelligence and Information Systems (IIS) there are several places
an engineer can go to get information concerning competencies, training opportunities and training they
have completed. There is no centralized source of this information that allows for a consolidation of this
data. Recently within IIS the systems engineering career paths have expanded to include additional career
options, thus adding to the complexity of the process and making this consolidation of information even
more important.
The concept for this paper is to provide a ”system architecture”-design and requirements to
consolidate employee data from three enterprise databases, producing a web page that can be used during
mid- and end of year performance reviews. This would allow a consolidated view of the Systems
Engineer (SE) employee’s training history, competency model compliance and skills as entered into the
skills database. This consolidation would allow a system engineer (SE), a supervisor and other
stakeholders to retrieve information that will assist in mentoring, career choices and reviews. This
interface is known in this paper as the Professional Development Interface (PDI).
The scope for this project is to develop a design and define requirements for the following:
• A web interface that provides horizontal and vertical mapping of each career path to skill-
sets, training and time in service for each person within SE.
• Direct access to the IIS SE Competency Models, PoSE Courses, SETDP, TTU SE
program, SMU Security Engineering and any other Raytheon offered classes.
• A map of a definitive career path, stepping through the appropriate levels regardless of
where an engineer starts
vi

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
The requirements and design for this paper follow the Raytheon Systems engineering
Cornerstones [Raytheon-1997] for system design and the basics taught within the TTU System
Architecture Class.
vii

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
LIST OF FIGURES
Figure 1.2-1 Identifying, Architecting and Allocating Requirements..........................................................2
Figure 2.1-1 Email........................................................................................................................................7
Figure 3.2.1-1 Contextual-Goals, Stakeholders/Viewpoints.......................................................................10
Figure 3.2.1-2 Contextual-Key Scenarios...................................................................................................12
Figure 3.2.2-3, Contextual-Quality Attributes............................................................................................13
Figure 3.2.3-4, Contextual-Context Diagram.............................................................................................15
Figure 4.1-1 Operational Concept...............................................................................................................17
Figure 4.3-1 Activity Diagram....................................................................................................................24
Figure 5.1-1 Figure Architecture Tradeoff Method Analysis (ATMA)......................................................26
Figure 5.1-2 Architecture Operational Content..........................................................................................27
Figure 5.2-3 Domain Collaboration............................................................................................................31
Figure 5.3-4 State Chart..............................................................................................................................32
Figure 5.4-5 Sequence Diagram..................................................................................................................34
Figure 6.2-1, Block Diagram......................................................................................................................36
Figure 6.2-2, Block Diagram......................................................................................................................37
Figure 6.5-5 COTS Product........................................................................................................................42
Figure 6.5-6 Interfaces................................................................................................................................43
Figure 6.5-7 PDI Web Page........................................................................................................................45
Figure 6.5-8, PDI Web Page continued......................................................................................................46
Figure 7.2-1-4 SE Vee [Forsberg / Mooz-2007].........................................................................................48
Figure 10.1-1, Raytheon Secure Access.....................................................................................................58
Figure 10.1-2, Save As Screen....................................................................................................................58
Figure A-1 A Typical Data Source Business Problem................................................................................75
viii

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
LIST OF TABLES
Table 1.4-1 Customer Expectations Prioritized............................................................................................5
Table 3.1-1 Quality Attributes & Priorities..................................................................................................9
Table 4.2.-1 Web Page Format...................................................................................................................19
Table 4.2-2 Database Updates....................................................................................................................20
Table 4.2.-3 Measurement..........................................................................................................................21
Table 8.2-1 Customer Requirements..........................................................................................................50
Table 9.3-1 Functional Requirements.........................................................................................................52
Table 9.3-2 CNs and FRs............................................................................................................................54
Table 10.1-1 PDI Derived Requirements....................................................................................................59

ix

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.
CHAPTER I
INTRODUCTION

1.1 Scope
This paper is in response to a request by the IIS Systems engineering Lead to develop
requirements to build a web page interface to consolidate employee data from three enterprise databases
that can be used during mid- and end of year reviews. This would allow a consolidated view of the
Systems engineer (SE) employee training history, competency model compliance and data entered into
the skills database.
The Scope of my individual assignment is to define the requirements and provide a design for
the following:
• A web interface that provides horizontal and vertical mapping of each career path to skill-
sets, training and time in service for each person within SE.
• Direct access to the IIS SE Competency Models, Principles of Systems engineering
(PoSE) Courses, Systems engineering Training and Development Plan (SETDP), Texas
Tech (TTU) Systems engineering Master’s program, Southern Methodist University
(SMU) Security Engineering and any other Raytheon offered classes.
• A systems engineering career path, stepping through the appropriate levels regardless of
where an engineer starts to show his/her progress.
1.2. Approach
The approach for the design and requirements for this paper followed the Raytheon Systems
engineering Cornerstones [Raytheon-1997] good system design and the basics taught within the TTU
System Architecture Class. Figure 1.2-1 provides a visual representation of the approach used throughout
this paper.

1

DISCLAIMER

The opinions expressed in this report are strictly those of the author and are not necessarily those of Raytheon, Texas Tech
University, or any U.S government department or agency.