| Role |
| Douglas Klugh is a Software Engineer, holding certifications in software process, implementation, and configuration management.
He has successfully delivered software solutions for commercial industries including banking, financial services, securities and investments, insurance, Internet, and logistics.
Doug has over 12 years of experience in this engineering role. |
| Discipline |
| Software Engineering is the application of disciplines which are used to construct highly reliable and maintainable software in a timely manner while effectively managing costs.
These software engineering disciplines provide a systematic and quantifiable approach to solving common issues related to software development.
Established software engineering disciplines include: |
| Business Modeling |
| Provides guidance on how to understand and visually depict a business.
It also provides guidance on developing the business use-case model, business analysis model, domain model, and the organizational context for the business. |
| Requirements |
| Elicits stakeholder requests and transforms them into a set of work products that scope the system to be built and provides detailed requirements for what the system must do.
Work products include a vision document, stakeholder requests, use-case models, glossaries, software requirements, software requirements specifications, supplementary specifications, and a requirements management plan. |
| Analysis & Design |
| Transforms requirements into work products specifying the design of the software while strategic and tactical decisions are made to meet the functional and quality requirements of a system.
Work products include an architectural proof-of-concept, software architecture document, user-interface prototypes, analysis models, use-case realizations, and data migration specifications. |
| Implementation |
| Develops, organizes, unit tests, and integrates the components based on the design specifications.
Work products include integration build plans, implementation subsystems, test logs, and implementation builds. |
| Testing |
| Evaluates and assesses the product quality.
Work products include testing strategies, test plans, test cases, test results, and change requests. |
| Deployment |
| Ensures a successful transition of the developed system to its users.
Work products include training materials and installation procedures. |
| Configuration Management |
| Controls and synchronizes the evolution of the set of work products composing a software system.
Work products include a project repository, a configuration management plan, project measurements, and change requests. |
| Environment |
| Defines and manages the environment in which the system is being developed, which includes process descriptions, configuration management, and development tools.
Work products include a development infrastructure, a development process, and project-specific templates and guidelines. |
| Project Management |
| Focuses on project planning, risk management, monitoring progress, and metrics.
Work products include a business case, software development plans, risk management plans, iteration plans, iteration assessments, and project measurements. |
| Software Process |
| Relates content elements into semi-ordered sequences that are customized to specific types of projects.
Thus, a process is a set of partially ordered work descriptions intended to reach a higher development goal, such as the release of a specific software.
These work descriptions are organized into a hierarchical breakdown structure.
A process focuses on the lifecycle and the sequencing of work in breakdown structures. |
|
| |
|
|
|
|