Ms. Laverne Currie has over 20 years of experience as a systems engineer at Boeing. She has a PhD in Systems Engineering and masters and bachelor's degrees in related fields. She has extensive experience leading engineering teams and developing processes to ensure systems integration, requirements management, and CMMI compliance. She is skilled in systems engineering, program management, and acting as a subject matter expert in areas like requirements development, verification and validation, and configuration management.

1. 1
Contractor
Laverne Currie has 20 years with Boeing Integrated Space & Security as a multi-task
systems engineer. Ms. Currie has successfully completed short and long-term projects. Ms.Currie has participated in
or led engineering activities within a driven methodology environment. Ms. Currie has work with military combat
systems procurement, acquisition, and systemprocesses. Ms.Currie has knowledge of systems engineering; mission
planning, requirements decomposition, verification/validation, interface, and design description (IDDs), as to identify
deficiencies, inconsistencies,and coordinate a close loop across teams.. In addition, oversee software configuration,
trouble shoot disconnects,test cases with team peers and developers,build reports, and request for changes across team
channels.
Ms. Currie has demonstrated and developed Capability Maturity ModelIntegration (CMMI), and accreditation process
(DIACAP), CISSP, and ISSEP. Ms. Currie has served as a primary technical liaison for systems engineering, architecture,
design,development of C4ISR, and security. Ms. Currie lead others to evaluate customer/operational needs to define system
performance requirements, integrate technical parameters and assure compatibility of all physical, functional and program interfaces.
Ms. Currie seeks out to identify solutions to reduce cost, risk, and to meet baseline design reviews. Ms. Currie is an energ etic leader,
team player, excellent people skills, and communication (written and verbal). In other words, Ms. Currie is a pioneer in the field of
systems engineering (but not limited to).
 Specialty: Systems thinking, managing & initiating
work, planning and organizing across functional
teams.Clearly convey information of ideas through a
variety of events to management,IPTs,suppliers,and
customers.
 Specialty: The ability to achieve desired outcomes on projects, on
time and within budget. Ability to define program objective, for
systems, segment, and subsystems. Awareness of standards,
processes, procedures, (but not limited to).
 Specialty: Analyze systems, customer, and product
requirements,look for consistency,gaps,or overlaps
to insure total vertical and horizontal integration.
Technical risks i.e., TPMs, KPPs, MOE, MOPs are
tracked, and evaluated.
 Specialty: The ability to lead diverse teams to resolve issues,
program driven events, and bring a closure to disconnects.
 Specialty: Effective Communication throughout the
product life cycle. Generate solution to problems &
process tools.Identify and recommendimprovements
, and adjustment within product life cycle events.
 Specialty: The ability to understand the big picture on programs and
including the impactof changes per requirements (i.e.,components,
plans, anticipate future event and minimizing risk).
 Specialty: Verification & validation, interface
integration, requirement management, requirement
development, operational requirements. Customer
knowledge and compilation of user needs.
 Specialty: Subject Matter Expert: Developing processes,Capability
Maturity Model Integration (CMMI), procedures, required
specifications, deliverables, and customers request.
 Specialty: Work towards a collaborative effort, Team
Player, defining & leading systems disciplines
throughout the program baseline.
 Specialty: Work as a mentor, adaptable to changeabilityand desire
to learn new things.
 Specialty: Seek challenging activities.Manage multi-
systems throughout product life cycle.
 Specialty: Effective communicator (written & verbal). Worked in
multi-discipline team environments.
 Leadership Style: Innovated, flexible, tolerant,
collaborative,people person, adaptable, and ethical.
 Specialty: Work independently,and lead others to produce technical
work responsive to customer needs.
Education: Steven’s Technology- PhD Program Systems Engineering (in progress),University of Redlands- Masters
Degree (MAM) Management “Information Systems”, Cal-State Long Beach University- Bachelor of Science degree,
Mechanical Engineer.

2. 2
Professional Career
(425) 999-2874 – email: Laverne_currie@aol.com
Transition to: Product Support Mgmt Engr. (2008-09) – AWS & P- 8A. Performed integration tasks
applied to multiple ISS IPTs (e.g. 40/45 ISS Change Board Focal/representative. (Open action items).
 Tracked open action items (IPTs/customers), and program disconnects for closure. Provided
technical information when requested. Supported IPTs on systems changes resulting from approved
changes. Posted current weekly, monthly status reports, and IPTs meetings. Developed processes,
procedures for program, and customers. Verified and validated Product Support requirements
(avionics). Tracked interfaces for impact and looking for gap disconnects cross teams.
Recommended and developed processes/procedures documents. Metrics (not limited to). Designed
a system to collect disconnects across integrated team. Results: Reduce impact, risk, cost, and user
friendly to Product Support IPTs.
Systems Engineer Security (FCS): (Seattle, WA) Serve as a Consultant/Subject Matter Expert (SME)
Processes process development). References requested.
 Subject Expert Matter, lead, focal and coordinator: Support establishment of processes to ensure
supportability/maintainability of products and services for Training, Dynamics Research Corporation
(DRC), Computer Sciences Corporation (CSC) Northrop Grumman Information (NGIT), and Logistic
Decision Support System (LDSS), Platform Soldier-Mission Readiness System (PS-MRS), Logistics
Data Management Service (LDMS), AT&T, and 5 components of Training Common Components
(TCC).
 Lead/exercised critical program information (CPI) process on 7 different functional groups. This
consists of participating in the CPI assessment process. Subject expert, included reviewing and
approval of the Program Protection Plans (PPP) provided by LSI One Team Partners (OTPs).
 Lead/worked closely with both One Team Partners (OTP) suppliers, and representatives of the Army
Research and Technology Protection Center.
 Lead/researched, documented, planned mitigation for critical program information, assisted in the
developing process improvement plans, and recommended improvement.
 Lead/Interacted with others to develop presentation materials, documents and data items for our OTP
and customers.
System (SoS) Architecture Team (FCS): (Seattle, WA).
 Systems Engineer for System of systems (SoS) Architecture team within the SoS Engineering and
Integration team. Assisted in the system analysis and problem resolution. Assumed responsibility for
various cross-functional working groups to support the SSEI Architecture team.
 Developed specifications, procedures, guidelines and process documentation.
 Allocated/integrated architecture requirements to lower tier manned and unmanned systems,
platforms, and subsystems developments.
 Performed as Focal/Coordinator for DoD/Army, IPTs, to collect, organizes, and incorporates data
descriptions, and functional behaviors (requirements), design attributes, environments, and standards
into a common architecture database. Focal for Modeling & Simulation (M&S) Team to solve
problems and give recommendation across IPTs team.
 Initiates, evaluate, coordinate and obtain approval to implement complex and cross-functional
engineering changes.
 Generated requirements and analyzes technical approach, SOW, WBS labor and deliverables for
workgroup, to ensure quality product is received.
 Identify and plan processes, tools and activities to develop an integrated support infrastructure.
 Developed documentation and training procedures for SoS architecture, and DoD/Army traceability
needs.
Core Site Systems Engineering Team (SEWG) (Seattle, WA) Serves as a Consultant/Subject Matter Expert
(in process development IDS). Certification: CapabilityMaturity Model Integration (CMMI) Carnegie Mellon University
(certified).

3. 3
 Systems Engineer Lead for developed the following documents: Systems Requirements Analysis,
Functional Analysis, System Synthesis, Systems analysis, Integration and Test, Interface
management, System verification, and Systems validation. Determining the scope of the system
requirements tier level (IDS), documenting the requirements definition in a system specification.
Section (2) Core Site Team: Requirements defined, work products defined and tagged to process
steps, Critical attributes defined. Process Documentation developed: Process Instructions (DPIs)
Systems Engineering Management Plan (SEMP), Interface Control, Interface Requirement Definition,
and mitigation plan. Template (TMP), Systems Engineering Management Plan (SEMP), Interface
Control, Interface Requirement Specification, and Interface Design Description. Systems Engineering
Requirement Management, Fault Analyses, and Requirement/Development (but is not limited to).
Developed and executed project plans. Results: CMMI Compliance for IDS. Coaches, counsels,
mentors and provides developmental understanding in Systems engineering. End Results: Boeing
CMMI Compliance.
AEW&C Program: (Seattle, WA) IPT/Lead SE Ground Support Segment (GSS):
 Systems Engineer/Lead assumed responsibility for system engineering support to Havelsan Seattle
(site). Assisted in system analysis and problem resolution, and defining, tracking project scope for the
ground level (sub-systems).
 Applied knowledge of multi-disciplinary processes and system engineering methodology and
techniques to develop, validate, and manage product-level segment/subsystem requirements to
ensure system integration.
 Participated in training and development for the on-site Havelsan team, and off-site customers.
 Coordinated interfaces (ICDs/IDDs), identify risk, resolved problems, between the segment and
subsystem IPTs. Performed requirement analysis, and management of requirements with DOORS
application. Gathering product information, delivery needs and converting their needs into creative
data item delivery solutions. Prepared application user guides, processes and specification per SOW.
Conveys organizational messages to facilitate the accomplishment IPTs, and process goals. Engaged
and empowered teammates to make process improvements, for PDR, CDR, and other technical
events.
 Addressed complex inquiries and provided technical assistance to customers.
“Closed Program” (Seattle, WA): Lead for systems engineering methodology and applied tools for a control
environment:
 System Engineer Lead: Developed the following documents: SE review & audit plan, requirement
development plan, requirement management plan, architecture & schema plan, Doors instruction plan,
Doors team charter plan, system process matrix procedure plan, requirement traceability plan, TPM
guideline plan, managed data procedure plan, corrective action process plan, “Watch” list procedure
plan, Top management outstanding issues plan, Watch list to support risk environment plan. Data
Control log development; open action data log, closed action log, open item comment log, definition
description log, tracking matrix (TPM, MOE, MOP, KPP), “Watch” list tracking log sheet, requirements
traceability matrix, engineering plan checklist, DOORS best practices, SE flow charts. Requirement
traceability for System specification, for validation. Identified and verified “Orphan” requirements, and
poorly written specification. Tracked and maintained open and closed action items status reports.
Identify the system architect definition of term functions. Support hardware and software SE functional
requirements. Developed several documents, plans, procedure, instructions (guidelines) to support
management data items, and customers’ needs.
“Closed Program” (Los Angles, CA) Lead: Failure Mode Effect Criticality Analysis (FMECA). Rockwell
 Systems Engineer Lead developed system engineering methodology processes for all
components. Responsible for tracking, and allocating the functional behavior requirements, and
physical high-level requirements. Status reports, and resolved complex problems, within the team
environment. Responsible for solving complex related problems to integrate SoS across a wide
spectrum, to support FMECA. Responsible to manage all requirements, develop all processes,
specifications, procedures, instructions per SOW.

4. 4
International Space Station, Propulsion Module (PM) (Seal Beach, CA): System Engineer for Avionics /
Propulsion subsystem hardware: Rockwell
 Systems Engineer Lead: Developed Tool application SRM, RTM, and DOORS database, for
requirements. Supported in the execution of design, verification, risks, FMECA, and reliability, a
historical database of processes.
 Develop and maintained open and closed action items status. Managed and developed the
requirement allocation and verification/validation process component level. Status reports on the
requirement allocation and decomposition process.
 Developed the following: Methodology process for system engineering, system engineering
management plan (SEMP), verification and validation (V&V), interface control document (ICDs) plan,
and guidelines. Travel required. Interface with customers in support of the SE processes to support
program baseline and action items. Lead systems engineer for Avionics: EPD&C, DPS,
Instrumentation, GN&C, and ICDs.
X37 Program (Seal Beach, CA): Rockwell
 Systems Engineer Lead: Developed and maintained the requirement traceability and allocation for the
system thru subsystems level.
 Developed the System Engineering Management Plan (SEMP), Verification and Validation Plan,
Interface Control document Mitigating Risk plan, documentation requirements for the component level.
 Designed subsystem functional and physical diagrams to support the baseline. Coordinated and
participated in all the system engineering meetings, demonstrated the system engineering (SE)
methodology process.
Teledesic (Seal Beach, CA): Rockwell
 Systems Engineer Lead: Developed System Engineering Management Plan (SATSEMP) that
described satellite system engineering process. The SATSEMP described an approach for
accomplishing the contractual obligations in the Technical Program Planning and Control, the System
Engineering Process, and in the Engineering Integration effort throughout the program. Designed a
methodology process to ensure compliance of evidence (as examples) to support customer needs,
and Design-to-Teledesic baseline proposal.
Ellipso (Seal Beach, CA): Rockwell
 Systems Engineer Lead: Worked independently to develop processes, verification and validation.
 Participated in resolving complex problems that required a high level of ingenuity and innovation.
Investigated and pursue courses of action necessary to obtain desired results.
 Supported technical requirement management for system engineering contract efforts. Such as, TRD
reviews, ORD interpretation and interface control methodology development.
 Generated the baseline-reviewed document for proposal development.
 Managed requirement allocations and verification methods.
 Continue process monitor and control (Configuration Management / Management Requirements)
throughout product lifecycle. Responsible to lead, direct development, integrate throughout the system
and engineering technical plans. Maintained Requirement Technical Management (RTM) application
hardware /software traceability.
GPS IIF: (Seal Beach, CA): Rockwell
 Systems Engineer: For the avionics spacecraft sub-system requirements, functional, and physical.
Developed the SE methodology process, specifications, polices, guidelines, procedures for a close loop
or open environment.
 Maintained requirements and compliance of all or part of the performance, functional and interfaces of
the avionic subsystems group.
 Developed the verification and validation allocation requirements. Monthly status reports to support the
subsystem components. Developed the functional and physical flow charts. Primary job task to assure

5. 5
requirements and decomposition traceability flow down to hardware and software. Continue process
monitor and control.
 Designed the configuration for the spacecraft sub-system (functional Block diagrams, ICDs, IDDs etc.)
(Tool -Auto Cad 14) Also, continued to support all IPTs such as; ADCS, EPS, TCS, SCP, TT&C &
Structure Mechanism, NaV Payload (Space Vehicle) in a variety of requirement job tasks.
Murdock, Inc, Compton, CA
 Draft Designer – for a several Aerospace EO’s revision Aircraft (C17) drawings
McDonnell Douglas Helicopter, Culver City, CA: (College student)
 Assisted in coordinating all pertinent data, editing, expense reports, monthly status report, technical
proposals and production programs contracts.
 Maintained notes, minutes, and action items to ensure execution of program strategy and direction.
 Reviewed and prepared program information data, briefings presentations and other materials as
required. Required interface with senior program and customer leadership. Coordinated test plans,
engineering orders, components parts, sub-vendors, and contract operations.
Employment History:
Hughes Aircraft Company, California 1983 to 1985
The McDonnell Douglas Company California 1988 to 1991
The Rockwell Company, California 1996 to 2003
The Boeing Company, California 2003 to 2004
The Boeing Company, Seattle, WA 2004-Current
_______________________________________________________________________________________________
Achievements/Certificate:
Systems Engineer –Internal & University.
System Architect USC and internal.
ManagementSeries,seminar & internal.
Leadership Organization seminars.
National Management Association (Active).
American Society of Mechanical Engineers,Oral Competition 1996.
Physic Hall of Fame Award, Academic Achievement & Role Model 1996.
Physics Scholarship Recipient1993.
Northrop Scholarship Recipient1991-95.
Fluor Daniel BS Engineering Scholarship Recipient1994-96.
Fluor Daniel MBA Engineering Scholarship Recipient1996-98.
Chevron Engineering Recipient1995.
Allied Signal Scholarship Recipient1995.
Tau Beta Pi Honor Society 1992 Certificate of Excellence (Peers).
Hughes Aircraft Scholarship Recipient1993.
TRW Scholarship Recipient 1991-92-94.
National Dean’s List1993-94 Book.
UML Rational Rose.
Lean 101.
Functional and Operational Analysis.
(Military/Process) DITCAP.
DAU Acquisition University.
Trade Study internal.
Risk Analyses internal.
Technical Design Reliability/Safety -Arizona University (Boeing recipient).
Space Mission Analysis and Design UCLA.
Tele-Communication certificate (USC).
CapabilityMaturity Model Integration (CMMI) Carnegie Mellon University(certified).
Fault Analyses (Dr. Ron Carson).
Project Management(PMI) Boeing & University.
Information Systems SecurityProfessional (CISSP).

6. 6
Information Systems SecurityEngineering Professional (ISSEP).
Supplier ManagementUniversity(SMU) Boeing.
Tools,Practices,and Metrics.
RequirementAnalyses internal & seminars.
RequirementDevelopmentinternal & seminars.
Functional Analyses.
Configuration Management(CM).
ISO Standards and Mil-Standards (Boeing).
DOORS Management.
Failure Mode Effect Critical Analysis (FMECA).
Familiaritywith exports controls and the International Traffic in Arms Regulations (ITAR).
Personal DevelopmentLeadership Training internal & seminars
Security Clearance: Secret (Active), TS (none active), SpecialSSBI (none active)
Retiree - Boeing 2012
Laverne E. Currie
SystemsEngineerSubjectExpert
cell (425) 999-2874
Email: Laverne_currie@Aol.com