Semat? Nice to meet you
And has anyone written anything about SEMAT here? We fix.
Seeing SEMAT - Software Engineering Method and Theory. It seemed reasonable. I am thinking about the possibility of using it in my projects. Analyzing risks. I would like to attract Habraraz.
SEMAT (Software Engineering Method and Theory) is an initiative for software engineering. The initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley.
The statement of the vision statement . There is a lot of effort for the initiative.
')
In September 2009, Ivar Jacobson, Bertrand Meyer and Richard Sowley launched the SEMAT initiative, which they outlined in their book The Essence of Software Engineering: Applying the SEMAT Kernel. The idea of ​​the trio was supported by programming gurus such as Barry Boehm, Ed Jordan, Scott Ambler, Larry Constantin and Bill Curtis. ABB, SAAB, IBM and Samsung have joined the work on SEMAT.
Regardless of the Scrum / RUP / ... / waterfall method, seven invariants are defined - alphas, which are common to all software systems. Dependencies are defined between invariants.
Each invariant in the course of the life cycle of a software system has a set of successive states.
For example, the Requirement alpha has the following set of states:
SEMAT also defines other entities: activities, jobs, competencies, which are absolutely necessary in software engineering.
Designed checklists that allow at each moment expertly assess the condition in which all alpha. Having the current state, we can compare the progress in all projects regardless of methods and technologies. In addition, knowing the next required state of alpha, we understand what needs to be done to get there.
Report of Ivar Jakobson in Google. Dr. Ivar Jacobson - The Essence of Software Engineering: The SEMAT Approach
Presentation
Report B.A. Pozina, Doctor of Technical Sciences, Professor, Chairman of the SEMAT Russian Chapter at Moscow State University - SEMAT. To the theory of software engineering. State and directions of development
Presentation
For fans of standards - Kernel and Language for Software Engineering Methods (Essence), OMG 11/11/2014 .
Three headlines of a few SEMAT articles for Russian media:
Yesterday ended the fourth scientific-practical conference "Actual problems of system and software engineering" (APSPI - 2015) , at which the workshop “SEMAT - a new methodology for software and systems engineering. Experience of use in 2013-2015. ” On the worksope with the report "Approach to Essence in the option for system engineering." A.Ilevenchuk , INCOSE Russian branch spoke .
Taki, yes! Are we “Russian programmers”? As always, we are ready to rewrite and summarize everything. Just in case - it was a joke.
Foreword
Seeing SEMAT - Software Engineering Method and Theory. It seemed reasonable. I am thinking about the possibility of using it in my projects. Analyzing risks. I would like to attract Habraraz.
Definition from Wikipedia
SEMAT (Software Engineering Method and Theory) is an initiative for software engineering. The initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley.
The statement of the vision statement . There is a lot of effort for the initiative.
')
Prehistory
In September 2009, Ivar Jacobson, Bertrand Meyer and Richard Sowley launched the SEMAT initiative, which they outlined in their book The Essence of Software Engineering: Applying the SEMAT Kernel. The idea of ​​the trio was supported by programming gurus such as Barry Boehm, Ed Jordan, Scott Ambler, Larry Constantin and Bill Curtis. ABB, SAAB, IBM and Samsung have joined the work on SEMAT.
Essence (very briefly)
Regardless of the Scrum / RUP / ... / waterfall method, seven invariants are defined - alphas, which are common to all software systems. Dependencies are defined between invariants.
Each invariant in the course of the life cycle of a software system has a set of successive states.
For example, the Requirement alpha has the following set of states:
- Identified
- Identified
- Clear
- Accepted
- Addressed
- Satisfied
SEMAT also defines other entities: activities, jobs, competencies, which are absolutely necessary in software engineering.
Designed checklists that allow at each moment expertly assess the condition in which all alpha. Having the current state, we can compare the progress in all projects regardless of methods and technologies. In addition, knowing the next required state of alpha, we understand what needs to be done to get there.
Meet more
Report of Ivar Jakobson in Google. Dr. Ivar Jacobson - The Essence of Software Engineering: The SEMAT Approach
Presentation
Report B.A. Pozina, Doctor of Technical Sciences, Professor, Chairman of the SEMAT Russian Chapter at Moscow State University - SEMAT. To the theory of software engineering. State and directions of development
Presentation
For fans of standards - Kernel and Language for Software Engineering Methods (Essence), OMG 11/11/2014 .
Well, finally
Three headlines of a few SEMAT articles for Russian media:
- “Will SEMAT turn on one hundred million programmers?”
- "SEMAT - the second revolution in software engineering?"
- "The science of programming is a means of catastrophe."
Well, the latest
Yesterday ended the fourth scientific-practical conference "Actual problems of system and software engineering" (APSPI - 2015) , at which the workshop “SEMAT - a new methodology for software and systems engineering. Experience of use in 2013-2015. ” On the worksope with the report "Approach to Essence in the option for system engineering." A.Ilevenchuk , INCOSE Russian branch spoke .
Taki, yes! Are we “Russian programmers”? As always, we are ready to rewrite and summarize everything. Just in case - it was a joke.
Source: https://habr.com/ru/post/258529/
All Articles