Preview

Itech6501 Principles of Software Engineering Tut2

Satisfactory Essays
Open Document
Open Document
475 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Itech6501 Principles of Software Engineering Tut2
GRADUATE SCHOOL OF INFORMATION TECHNOLOGY
AND MATHEMATICAL SCIENCES
ITECH3501/ITECH6501 Principles of Software Engineering

Tutorial Two

Requirements Definition Marks1

1. In which development situations would it be unnecessary or even detrimental to define requirements?

Some of non-functional requirements are not necessary for some development situation. Sometimes team has to develop some small functionality, for example some update or additional function, etc. In this case follow to all non-functional requirements bring excess price and time spending.

2. What are the most frequent types of requirement errors and why are they critical for the final product?

According to TechRepublic.com’ article, there are 5 most frequent types of requirement problems: • Usually customers do not know what they exactly want • Requirements alter during all project lifecycle • Customers do not understand real timelines • Communication problem between customers, engineers and project managers • Development teams do not understand customer company politics. (TechRepublic.com, 2007) All of these problems may result of wrong requirements gathering, of course it will be a result of serious errors in requirements. The errors are causes of extra costs or even a project failure.

3. What are non-functional requirements and how do they relate to functional requirements?

“A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions… Non-functional requirements are often called qualities of a system” (Wikipedia, 2013).

There are 49 examples of non-functional requirements: Accessibility, Audit and control, Availability, Backup, Capacity, Certification,

You May Also Find These Documents Helpful

  • Satisfactory Essays

    Database Concepts Pt2520

    • 326 Words
    • 2 Pages

    1. TRUE A requirement is something a database needs to do in order to fulfill its purpose.…

    • 326 Words
    • 2 Pages
    Satisfactory Essays
  • Better Essays

    Nvqlevel 2 Unit 201&202

    • 1124 Words
    • 5 Pages

    1.8 Types of problems that can occur at work and prevent you to complete your task as plan…

    • 1124 Words
    • 5 Pages
    Better Essays
  • Good Essays

    Project Management

    • 694 Words
    • 3 Pages

    Requirements traceability involves linking a requirement backwards to an actual business need and forwards to the ending product or service. Requirements are also linked to other requirements (Kerton, 2011). Requirements traceability benefits an organization by allowing it to improve scope management, improve test coverage and test costs, and improve impact assessment (Kerton, 2011, p. 2-3). A properly completed requirements traceability matrix allows an organization to clearly identify risks within the improved business process, as well as any opportunities and threats.…

    • 694 Words
    • 3 Pages
    Good Essays
  • Satisfactory Essays

    Term Paper

    • 291 Words
    • 2 Pages

    Sample issues are listed below; however, feel free to expand this list to back up your summary position.…

    • 291 Words
    • 2 Pages
    Satisfactory Essays
  • Better Essays

    Im/It Service Management

    • 1910 Words
    • 8 Pages

    2) Unauthorized changes: Engineers do not follow the change management process, making mistakes harder to track and fix.…

    • 1910 Words
    • 8 Pages
    Better Essays
  • Satisfactory Essays

    Database Sql Server

    • 328 Words
    • 2 Pages

    A requirement is something a database needs to do in order to fulfill its purpose. True…

    • 328 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Hank Kolb

    • 326 Words
    • 2 Pages

    The groups of problems defined above are the materials for the fishbone diagram. Within this fishbone diagram we can see the cause and effect relationship and how these smaller problems lead to poor quality assurance as a whole…

    • 326 Words
    • 2 Pages
    Satisfactory Essays
  • Good Essays

    Software Engineering

    • 985 Words
    • 4 Pages

    I have many goals in mind for my life. I want to graduate university, possibly go to graduate school, and obtain a career in which I am happy and satisfied. Yes, I know this sounds very cliché as many people want to obtain this kind of life. I don’t mind obtaining a “normal” happy life as long as I am happy with it. I am familiar with Maslow’s Hierarchy of Needs and I want to make sure I fulfill my lower needs before I start trying to achieve my goals. I have never actually applied the GIOADA process to my decision making in the past. After reading the document that describes the GIOADA process, I will start applying this process to future decisions I make in life. Also, as I look back at some of the big decisions I made previously, I wish I applied the GIOADA process in making these decisions. That would have allowed me to more strongly analyze all the processes of the decision making.…

    • 985 Words
    • 4 Pages
    Good Essays
  • Better Essays

    Supply Chains

    • 3293 Words
    • 14 Pages

    Functional Products are generally staples or those generally bought from the grocery stores or retail outlets. They have stable demands are price variations do not affect the demand drastically. Such products have long life cycles but they invite competition and usually have low profit margins.…

    • 3293 Words
    • 14 Pages
    Better Essays
  • Powerful Essays

    The common requirement error is due to human (i.e lack of Communication between customer and the analyst), software, etc.…

    • 2331 Words
    • 10 Pages
    Powerful Essays
  • Satisfactory Essays

    Kirk Patrick Samuda,

    • 326 Words
    • 2 Pages

    interface. A lot of times, requirements are omitted or left out because people assume there is no…

    • 326 Words
    • 2 Pages
    Satisfactory Essays
  • Good Essays

    There are several reasons why the project has run into problems. Some of these could have been foreseen but some not.…

    • 1013 Words
    • 3 Pages
    Good Essays
  • Good Essays

    Accounting Software Memo

    • 411 Words
    • 2 Pages

    This analysis should help you develop a requirements definition. A requirements definition will tell you what the business needs from the software. These items I have mentioned above will help the process go smoothly and ensure that no critical functions needed from the software are missed.…

    • 411 Words
    • 2 Pages
    Good Essays
  • Good Essays

    This section enumerates three dozen classic mistakes. I have personally seen each of these mistakes made at least once, and I've made many of them myself. You'll recognize many of them from Case Study 3-1.…

    • 4203 Words
    • 17 Pages
    Good Essays
  • Good Essays

    One of the most common mistakes by new analysts is to confuse functional and nonfunctional requirements. Given the following list of requirements for a sales system:…

    • 325 Words
    • 2 Pages
    Good Essays