![]() If no one decides to do architecture, then a default one happens that is probably poor. I'm trying to keep it a summary.) I'll end with: Even if it seems your project has no formal architectural or design stage/AOR/documentaiton, it IS happening whether anyone is consciously doing it or not. Design and even architectural decisions must bemade later in the project whether that is the plan or not.Įven if the stages or areas of responsibility blend together and happen all over the place, it is always good to know what level of decision-making is happening. Software development is complicated and difficult to plan anyway, but clients/managers/salespeople usually make it harder by changing goals and requirements mid-stream.There are often more iterations where the whole process happens over and over. Design (architecture to a lesser extent) takes place throughout the SDLC on purpose. ![]() Newer ways of thinking about the SDLC (see Agile methodologies) somewhat rearrange this traditional approach.(There are already existing databases, conventions, standards, protocols, frameworks, reusable code, etc.) A project might be a part of a larger project, and hence parts of both stages are already decided.Smaller projects often don't have enough scope to separate out planning into these to stages.These two stages will seem to blend together for different reasons. Specification are written during this stage. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |