2 deleted 5 characters in body
source | link

If you don't take the time for proper development, you will spend 10 times that time fixing the software in production. Worse, you could loose the job and cost your company.

Most of the trouble developers face can be attributed to commitments made about delivery time of a project. Be clear with your management about the need for time.

If the company has no resources, maybe they could:

1-Give priority to the most required parts of the system and ask you to do the top ones in the given time 2-Hire more people to help 3-Buy a ready-made software that works, even if it does not do all the work required

Your questions cover the entire litrature of software engineering and requirements management as well other parts of the software spectrum, so it is impossible to give you a complete answer but here is a quick one.

How should I :

1- List out Requirements for myself. (Not an official document) 2- How to verify and validate the requirements ? 3- How to visualize them ? 4- How to design them with minimum effort ? (As its going to be with me only)

Answer 1: You have to break the business area into smaller ones (if it is big) - document input data and business rules clearly for each in clear and concise language and present it as a readable list. Try to build some use cases for critical activities.

Answer 2: The deliverables of answer 1 above together with the questions you will come up with during finishing the above task will help you ask the customer to work with you on verifying the requirements.

Answer 3: Convert results from 1 and 2 into a class diagram and/or ERD, Use Cases and Sequence Diagrams or BPM diagrams.

Answer 4: Use tools such as ORM, 3rd party GUI components and Code Generators if you could.

You must clearly understand:

  • System objectives

  • Different types of users of your system and security implications

  • What is the best platform for the solution

  • Documentation is not a waste of time

  • User communication is a must - Involve them early

  • Management involvement and communication is a must - Involve them early

  • Realistic goals and estimations are a must

Good luck Also

If you don't take the time for proper development, you will spend 10 times that time fixing the software in production. Worse, you could loose the job and cost your company.

Most of the trouble developers face can be attributed to commitments made about delivery time of a project. Be clear with your management about the need for time.

If the company has no resources, maybe they could:

1-Give priority to the most required parts of the system and ask you to do the top ones in the given time 2-Hire more people to help 3-Buy a ready-made software that works, even if it does not do all the work required

Your questions cover the entire litrature of software engineering and requirements management as well other parts of the software spectrum, so it is impossible to give you a complete answer but here is a quick one.

How should I :

1- List out Requirements for myself. (Not an official document) 2- How to verify and validate the requirements ? 3- How to visualize them ? 4- How to design them with minimum effort ? (As its going to be with me only)

Answer 1: You have to break the business area into smaller ones (if it is big) - document input data and business rules clearly for each in clear and concise language and present it as a readable list. Try to build some use cases for critical activities.

Answer 2: The deliverables of answer 1 above together with the questions you will come up with during finishing the above task will help you ask the customer to work with you on verifying the requirements.

Answer 3: Convert results from 1 and 2 into a class diagram and/or ERD, Use Cases and Sequence Diagrams or BPM diagrams.

Answer 4: Use tools such as ORM, 3rd party GUI components and Code Generators if you could.

You must clearly understand:

  • System objectives

  • Different types of users of your system and security implications

  • What is the best platform for the solution

  • Documentation is not a waste of time

  • User communication is a must - Involve them early

  • Management involvement and communication is a must - Involve them early

  • Realistic goals and estimations are a must

Good luck Also

If you don't take the time for proper development, you will spend 10 times that time fixing the software in production. Worse, you could loose the job and cost your company.

Most of the trouble developers face can be attributed to commitments made about delivery time of a project. Be clear with your management about the need for time.

If the company has no resources, maybe they could:

1-Give priority to the most required parts of the system and ask you to do the top ones in the given time 2-Hire more people to help 3-Buy a ready-made software that works, even if it does not do all the work required

Your questions cover the entire litrature of software engineering and requirements management as well other parts of the software spectrum, so it is impossible to give you a complete answer but here is a quick one.

How should I :

1- List out Requirements for myself. (Not an official document) 2- How to verify and validate the requirements ? 3- How to visualize them ? 4- How to design them with minimum effort ? (As its going to be with me only)

Answer 1: You have to break the business area into smaller ones (if it is big) - document input data and business rules clearly for each in clear and concise language and present it as a readable list. Try to build some use cases for critical activities.

Answer 2: The deliverables of answer 1 above together with the questions you will come up with during finishing the above task will help you ask the customer to work with you on verifying the requirements.

Answer 3: Convert results from 1 and 2 into a class diagram and/or ERD, Use Cases and Sequence Diagrams or BPM diagrams.

Answer 4: Use tools such as ORM, 3rd party GUI components and Code Generators if you could.

You must clearly understand:

  • System objectives

  • Different types of users of your system and security implications

  • What is the best platform for the solution

  • Documentation is not a waste of time

  • User communication is a must - Involve them early

  • Management involvement and communication is a must - Involve them early

  • Realistic goals and estimations are a must

Good luck

1
source | link

If you don't take the time for proper development, you will spend 10 times that time fixing the software in production. Worse, you could loose the job and cost your company.

Most of the trouble developers face can be attributed to commitments made about delivery time of a project. Be clear with your management about the need for time.

If the company has no resources, maybe they could:

1-Give priority to the most required parts of the system and ask you to do the top ones in the given time 2-Hire more people to help 3-Buy a ready-made software that works, even if it does not do all the work required

Your questions cover the entire litrature of software engineering and requirements management as well other parts of the software spectrum, so it is impossible to give you a complete answer but here is a quick one.

How should I :

1- List out Requirements for myself. (Not an official document) 2- How to verify and validate the requirements ? 3- How to visualize them ? 4- How to design them with minimum effort ? (As its going to be with me only)

Answer 1: You have to break the business area into smaller ones (if it is big) - document input data and business rules clearly for each in clear and concise language and present it as a readable list. Try to build some use cases for critical activities.

Answer 2: The deliverables of answer 1 above together with the questions you will come up with during finishing the above task will help you ask the customer to work with you on verifying the requirements.

Answer 3: Convert results from 1 and 2 into a class diagram and/or ERD, Use Cases and Sequence Diagrams or BPM diagrams.

Answer 4: Use tools such as ORM, 3rd party GUI components and Code Generators if you could.

You must clearly understand:

  • System objectives

  • Different types of users of your system and security implications

  • What is the best platform for the solution

  • Documentation is not a waste of time

  • User communication is a must - Involve them early

  • Management involvement and communication is a must - Involve them early

  • Realistic goals and estimations are a must

Good luck Also