#requirement engineering

[simpler7045]

Specification for A-SPICE or ISO 26262

Specification for A-SPICE or ISO 26262

In the A-SPICE, there are various kinds of requirements; System Requirement, System Design, SW Requirement, SW architecture, SW Unit design. ISO 26262 requires similarly .

To manage traceability rigid decomposition of requirements into these are beneficial.

You can integrate all kinds of requirements into one documents. Then you will face a fact that managing traceability is not a easy task.

To…

View On WordPress

[simpler7045]

Learning to work with user stories

Learning to work with user stories

Learning to work with user stories

http://niksilver.com/2019/03/26/user-stories/ — 사이트 계속 읽기: niksilver.com/2019/03/26/user-stories/

use case diagram or user story is considered in the business level, and if I map to development process, it is very close to ConOps or SOTIF level.

In some cases, we can try to use user story to sub-system’s development process, then it would be hard to make fit.…

View On WordPress

[chintantakwani-blog]

Class diagrams

Class diagrams are structural UML diagrams which depicts the static view of application. They are very important from analysis and design point of view. Behavior diagramsindicate the behavior of the system while class diagrams can be helpful while designing the application too. It contains attributes and operation hence representing the encapsulation property of object oriented programming…

View On WordPress

[simpler7045]

시스템 및 소프트웨어 요구사항 관리 방법?

시스템 및 소프트웨어 요구사항 관리 방법?

휴가중에 최근 어떤 분이 다음과 같은 문의를 해주셨다. “어떤 경우 시스템 요구사항과 소프트웨어 요구사항이 겹치는 것 같다. ”   이 부분은 어느정도 사실이다. 그리고 좋은 현상이다. 다만 시스템의 scope와 소프트웨어의 scope간의 경계를 어떻게 정할 것인지에 대해서 약간은 명확하지 않아서 어려움을 겪고 계신 것이라고 생각한다. 요구사항을 작성하려면 그게 sys일지 sw일지에 대해서 생각해 보지 말고, 일단 interface가 어떤 형태일지 생각해보자. interface가 작성하고자 하는 요구사항의 scope가 된다. 꼭 sys로 작성하고 sw로 한번 더 작성해야 한다고 생각할 필요는 없다. 장난감을 만드는 경우라면 굳이 분리하는 것이 의미가 없을 수도 있고, 거대한 것을 만드는 경우라면 분리를…

View On WordPress

[simpler7045]

Requirement elicitation and analysis (요구사항 수집 및 분석)

Requirement elicitation and analysis (요구사항 수집 및 분석)

한국어는 아래로 스크롤.. When doing SW certification consulting, most customers are conceptually aware of what they need to develop and know roughly how to implement it. So the requirements collection and analysis phase was not too difficult. However, in the project I am participating in, the customer did not have requirements. Obviously, there exists what we have to do, but the concept of what our team…

View On WordPress

[ifourconsultancy]

An introduction of requirement engineering, Requirement Development and Requirement Management for software projects in IT companies India.