Good Morning I read your article and I have a question related to one of the component based software development life cycle. I hope that you could help me!
I read about "Y model component based software development life cycle" since I have to use it n my graduation project . However, I have some questions:
- Why there is repetition in the outcome of the phases ( e.g: domain engineering and system analysis.. or .. frameworking and design )?
- It was mention that there is overlap between the phases, but I didn't see anything in its diagram that indicate overlapping?
- Suppose that an expert will use it: the expert will follow top-down approach and thus will start from system analysis. In this case, would he go for framworking and domain engineering after finishing the assembly/archiving phase? or he will simply ignore these phases? But if he ignore them, I think the SDLC will be similar to water fall , am I right?
Thanks in advance
Leave a Reply
Your email address will not be published. Required fields are marked *
KHadija
Good Morning
I read your article and I have a question related to one of the component based software development life cycle. I hope that you could help me!
I read about "Y model component based software development life cycle" since I have to use it n my graduation project . However, I have some questions:
- Why there is repetition in the outcome of the phases ( e.g: domain engineering and system analysis.. or .. frameworking and design )?
- It was mention that there is overlap between the phases, but I didn't see anything in its diagram that indicate overlapping?
- Suppose that an expert will use it: the expert will follow top-down approach and thus will start from system analysis. In this case, would he go for framworking and domain engineering after finishing the assembly/archiving phase? or he will simply ignore these phases? But if he ignore them, I think the SDLC will be similar to water fall , am I right?
Thanks in advance