COURSE # SRO-657
OBJECT-ORIENTED SYSTEMS ENGINEERING METHODOLOGY - An Overview of OOSEM
Timely, concise review of the System Level benefits gained when implementing Object-Oriented Systems Engineering Methodology, OOSEM.
Object Oriented Programming, OOP, gained prominence and evolved as a preferred methodology in many applications. This two-day class introduces and explores the latest Object-Oriented Systems Engineering Methodology (OOSEM). Class participants will also investigate the OOSEM as a way to more effectively and efficiently interface with Software Engineering throughout the full System Lifecycle.
The emphasis of this class is on assisting Systems Engineers in understanding the merits of learning and implementing OOSEM (i.e., smoother interfaces between systems and software engineering throughout the full system lifecycle), rather than on the technical details of implementation methods (i.e., specific Unified Modeling Language (UML) implementation details).
Applications and benefits:
You will benefit by enhancing your understanding of the:
- Object Oriented concepts.
- Structured Analysis/Structured Design Systems Engineering Methodology (SA/SDSEM).
- OOSEM objectives.
- System Level and Full Lifecycle benefits.
Who should attend:
This course is designed primarily for Systems Engineers, Managers and Supervisors experienced with OO design and SA/SDSEM, but interested in investigating OOSEM as a way to more effectively and efficiently interface with Software Engineering throughout full system lifecycles. The course objective is to familiarize the participants with the reasons for, and the benefits of, adopting OOSEM.
The prerequisite for this course is a working knowledge of OO and SA/SDSEM.
Course Outline:
Material presented (and practiced) during the two-day overview of OOSEM addresses the following Questions/Issues:
- Why Should We Want To Take This Class In The First Place?
- A Review Of Structured Analysis/Structured Design Systems Engineering Methodology (SA/SDSEM)—One More Time!
- What Do Software Engineers Do Anyway?
- So What’s The Difference Between Them And Us?
- The Historical SE And SWE “Tower of Babel”.
- Object-Oriented Systems Engineering Methodology (OOSEM). Ready Or Not…
- What Brought On All This OOSEM Talk Anyway? What Have I Been Doing Wrong?
- Years Of Doing SA/SDSEM And All Of A Sudden OOSEM?
- What’s The Difference Between OOSEM And SA/SDSEM Anyway?
- How Compatible Really Is OOSEM To What Software Engineers Have Been Doing?
- Just A Taste Of Object-Oriented Concepts And UML—So’s Not To Scare Anybody Away
- Who Else Is Even Interested In OOSEM?
- Has Anybody Actually Made OOSEM Work?
- How Come OOSEM Hasn’t Already Caught On?
- So What If I Get Smart On OOSEM? Who’s Going To Let Me Use It?
- Okay. The Light Bulb Is On. Now What Do I Do With My New-Found OOSEM Smarts?
- What’s Really Going To Happen When I Try To Shoehorn OOSEM Into My Ongoing SA/SDSEM) Work?
- Are You Going To Leave Me To Learn OOSEM On My Own, Or Do You Have Something To Help Me?
- Any Real, ‘No-Kidding’ Places We Can Go For OOSEM Guidance, and Advice?
The material presented is the product of combined expertise in this field, and is supported by the following extensive list of references and instructor’s experience:
OOSEM Training at JHU/APL:
OOSEM Tutorial; “Object-Oriented Systems Engineering Methodology”; JHU/APL; Friedenthal; 28 October 2000
OOSEM Tutorial; JHU/APL; Object-Oriented Systems Engineering Methodology; JHU/APL; Friedenthal, Lykins; 20 October 2001
OOSEM Tutorial; “Developing Real-Time Systems Using Real-Time UML”; JHU/APL; VanZandt; 21 September 2002
OOSEM-Related Contacts:
Fellow members of the International Council on Systems Engineering (INCOSE) Chesapeake and WMA Chapters.
Fellow Systems and Software Engineers at the Johns Hopkins University Applied Physics Laboratory (JHU/APL) working on various SE and SWE projects.
Fellow Systems and Software Engineer members of the JHU/APL “UML Users Group”.
Fellow Team Members (Government, JHU/APL, and Contractor) working together on Departmental and Enterprise-Wide Systems Engineering and Architecting projects at the National Security Agency.
OOSEM WWW URLs:
About the Instructor
Michael E. Pafford, M.S., brings more than 30 years of experience in the design, architecture, integration, operation, and management of intelligence-related systems. He is currently a Senior Systems Engineer in the Intelligence Systems Group at the Johns Hopkins University Applied Physics Laboratory working on analyzing and modeling Enterprise-Level Performance Assessment methodologies for the Community ELINT Management Office (CEMO). He led the JHU/APL technical team in the development of C4ISR Architecture products in support of the Chief Engineer of the Navy’s Time-Critical Targeting and Tasking, Collecting, Processing, Exploitation, and Dissemination Mission Capability Packages. Mr. Pafford began his career as an Air Force Signals Intelligence Specialist. Later he served as a Navy Cryptologic Officer leading the design of state-of-the-art intelligence, surveillance, and reconnaissance systems. After retiring from active duty, Mr. Pafford held senior systems engineering positions with ITT, General Dynamics, and Harris Corporation where he led technical teams in the architecting, development, and integration of GFE, GOTS, and COTS intelligence systems for DoD customers.
Details:
Course: SRO-657 Duration: 2 Days FEE: $1,199 CEUs: 1.44
Please direct any additional inquiries regarding our courses to Zygmond Turski, Program Director, by e-mail, FAX: (240) 371-4488 or TELEPHONE: (636) 273-9608.
Call toll free 1-800-683-7267 from anywhere in the Continental U.S. or CANADA.
Last modified April 6, 2008.
