Morning,

In my experience, different people, different teams, different departments, different companies, different industries, different cities and different countries all have different meanings for these documents. Some may not have them both or call them something else entirely or have extra documents. Some may use different people to complete each document, some may be done by the same person, etc.

Like Adrian said, you just need to work out what it means in your company or department or team and create templates accordingly. First question I ask at an interview is "What are the deliverables?". Second question is "What information should go into that deliverable?".

Kimbo

It depends on the domain.

If the business is the domain, the requirements are written in such a way to satisfy the business needs. eg. The member borrows books from Library (where the Library is the domain - square box in use case).

If the sqaure-box is the computer system, the Functional requirements is different. eg. The Librarian checks out the book; (and hands it to the Member).

In one instance the member interacts with the business (the library); in another the member gives the book to the librarian who then checks out the book using the system.

The usecases depicting these activities are different. The business usecases have a diagonal line through the head of actor and the usecase (oval) etc.

Just some thoughts.

K

Requirements document can have Functional and Non-Functional Requirements. You can have a REquirements doc which lists all Non-functional Requirements and have a seperate Functional Docs.

Regards,

Maria Iqbal

www.futurethoughtsllc.com