Goutham
asked on
software development methodology
Dear Experts
Would like to know the sequence of software development methodology, please correct me on the below if found it incorrect or sequence found to be changed
1. Requirement study and documentation by business analyst
2. Solution architect will convert the requirement document to design document/functional specs
3. Solution architect will prepare the technical specifications for developer to start developing
4. Test strategy will be prepared by QA team
5. Testers -
User acceptance will be done by customer
Please let me know is the above in sequence and is there anything which can go parallel or one after another also where does UI/UX come into in the above sequence also document writing for user manual or operational manual
Would like to know the sequence of software development methodology, please correct me on the below if found it incorrect or sequence found to be changed
1. Requirement study and documentation by business analyst
2. Solution architect will convert the requirement document to design document/functional specs
3. Solution architect will prepare the technical specifications for developer to start developing
4. Test strategy will be prepared by QA team
5. Testers -
User acceptance will be done by customer
Please let me know is the above in sequence and is there anything which can go parallel or one after another also where does UI/UX come into in the above sequence also document writing for user manual or operational manual
ASKER
thanks for the update, can you please help considering the waterfall methodology please
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
but in general, you need to think about the software development life cycle, whether it's some kind of traditional way like Waterfall versus what we usually emphasize these days by using Agile/ Scrum methodologies and look for their differences.