Contributions for June Issue of The Best Practice Magazine:
Submit your article about VAL/VER - *Validation / Verification for next month's Issue of The Best Practice Magazine. Congratulations to David P. Quinn who had most views for his May 2018 article entitled Demonstrating Best Value in Supplier Selection. Send your Articles / Presentations / Tools to This email address is being protected from spambots. You need JavaScript enabled to view it.
CMMI Articles/Presentations - RD/TS/PI
*Requirements Development / Technical Solution / Product Integration
RD Summary The purpose of Requirements Development (RD) (CMMI-DEV) is to elicit, analyze, and establish customer, product, and product component requirements.
TS Summary The purpose of Technical Solution (TS) (CMMI-DEV) is to select, design, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product related lifecycle processes either singly or in combination as appropriate.
PI Summary The purpose of Product Integration (PI) (CMMI-DEV) is to assemble the product from the product components, ensure that the product, as integrated, behaves properly (i.e., possesses the required functionality and quality attributes), and deliver the product.
The CMMI® is an integrated set of best practices that improve performance and key capabilities for any organization that wants to develop better products, components, and services.
In a first posting on the CMMI roadmaps for CMMI V1.3, I described how the project roadmap has been improved to deliver an even better result. In this posting I’m covering the product and the product integration roadmap.
"CMMI Requirements Data used to Quantify “Should Cost” Software Development and Risk" SEI CMMI Requirements data from Real Time (RT) systems assembled by the SEI is used to show how software development estimates are made and risk assessed at the early Concept stage. This Requirements data is frequently more available in less complex application categories including Engineering, Scientific, Telecommunications, Business Systems etc.
https://www.mitre.org Some of the frameworks are concerned with "what" should be done and others focus on "how" it should be done. Frameworks such as CMMI are in the "what" category. For example, CMMI indicates the need for a requirements development process area. It involves establishing customer and product requirements and analysis and validation. However, it does not prescribe elements such as what approach to use, the process model, or what rules to follow.
The objective of TS is to design (developing architecture, high level and low level/detail design), develop (coding or data conversion activity for Data migration), and implement (successful deployment at the customer’s site) solutions as per agreed and documented requirements (as per the requirements management and development activities/phase). This includes products, PCs (programs or modules), and product-related lifecycle processes (user manual, design manuals etc). The objective of PI is to ensure planned successful assembling of the complete product (or services) from one or more, simple or complex PCs (or service components), ensuring that the product (or services), as integrated, functions properly as intended by design, and deliver/deploy the product (or services) at the end user/customer site.
SCRUM Articles/Presentations - RD/TS/PI
*Requirements Development / Technical Solution / Product Integration
Background A common concern with Agile software development at the enterprise level is that it does not scale well. There are different approaches to scaling Agile methods to address enterprise concerns. Many of the concepts such as using small, self-managing teams, work well for small projects. However, challenges increase when coordinating multiple teams working on a large-scale, complex project with numerous iterations to deliver releases that provide stakeholder value.
COBIT Articles/Presentations - RD/TS/PI
*Requirements Development / Technical Solution / Product Integration
ABSTRACT With increasing demand for software products with high „Quality‟, it has become imperative for organizations to adopt quality models like (International Standard Organization) ISO 9001,(Capability Maturity Model Integration)CMMI or Six Sigma etc. to set and sail on their quality journey. The strong emphasis on Software Quality Assurance in these models coupled with the modern day mantra of “Prevention”, the need for pro-active Quality Assurance is higher than ever.
Six Sigma Articles/Presentations - RD/TS/PI
*Requirements Development / Technical Solution / Product Integration
While there are more than a few connections between the Six Sigma DMAIC roadmap and Capability Maturity Model Integration (CMMI), some practitioners may not be aware of the connections between CMMI and Design for Six Sigma (DFSS). CMMI has four process categories, each contains several process areas that are associated with a maturity level (Table 1). Process areas most strongly connected to DFSS are those in the engineering process category.
AI - RD/TS/PI
*Requirements Development / Technical Solution / Product Integration
Our purpose in this thesis is to investigate the current artificial intelligence applications in scope of the CMMI process areas. Firstly, research is made regarding the CMMI Model. Then, current studies about CMMI process areas by using artificial intelligence techniques were examined.
