His first attempt was called Objectory, which was bought by a larger company and lead to Rational Unified Process, which was generalized to be less proprietary into the Unified Software Development Process (Unified Process, or UP in short). When Ivar Jacobson invented use-cases he aimed at a development method that would be driven by the use-cases and allow to methodically derive the implementation from the use cases. help me to create class diagram ? Is this also right way ? Now till here, am I going right ? Does notations used in use-case such as include, extend etc. So, I created a use-case cards and now I am planning to write use-case cards for each functional requirements then also write a sequence diagram for each use-case card. Please verify me here, what I know is that input of use-case are functional requirements. As gathering non-functionals, I also classified them scalability, performance, regulatory, design contrains etc. Anyway, I started to gathering and classfying requirements as non-functional, functional, business, stakeholder etc. Now, I am alone on my way with nearly 700 pieces of well written product requirements. We started to create product specs->HLR->DLR on EXCEL. Later, new project lead took over the project and started from the begining with applying V-model. So far, the project moved with a zero- architecture documentation to give an output as fast as possible. In my current project, at the beginning, I was only responsible for only software development and the Team consisted of 3 people.īut, as time passes, hardware eng. I am coming from the Embedded Systems domain with more than 3 years experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |