System Development and Testing: Agile Manifesto, User Stories, Use Case Diagrams, Code Quality, Test

Agile Manifesto

The purpose of the "Agile Manifesto" was to recommend principles for system development which would overcome the disadvantages of traditional methodologies such as "waterfall". List and explain TWO of its recommendations: Your answer:

Identify the types of graphical models you would use to model each of the following:

i.the functionality of the system at the requirements capture stage of the project

ii.the actions required to implement a specific functional requirement

iii.the screen design and navigation of the user interface at the late design or early implementation stage

iv.the relationships between classes at the design stage of the project Your answer:

What is the purpose of "user stories" (or "user scenarios") in system development?

On a use case diagram, use cases may be linked by either an <<include>> or an <<extend>> line. Explain the difference between these two types of relationships Your answer:

Explain the purpose of a "wireframe" Your Answer:

Explain the difference between "static" and "dynamic measures for assessing code quality, and give one example of each Your answer:

Below are four stages in testing software.  Explain the purpose of TWO of these stages

·unit testing

·integration testing

·system testing

·acceptance testing.

“Parallel running” and “cut-over” are two different approaches to releasing new systems to users.  Explain each term and identify one key differences between them in terms of service management.

A developer working for Company AAA develops a software application. Company BBB requires a similar application but tailored to their products. They offer the developer a job at a much higher salary provided he/she brings their application with them. Identify the professional issues in this scenario and suggest how the developer should behave before accepting the job with Company BBB.

What is the purpose of a "Repository" in a project management software and how is it used by the project team.

This question relates to the Orinoco Order processing System Case Study

Orinoco is a company providing specialist multi-media items e.g. DVDs, CDs, vinyl records, cassette tapes, books. The company does not keep items in stock, but acts as a broker between buyers and sellers. They require a system Orinoco Order Processing System - OOPS) that provides a website for sellers to post items and buyers to buy items or post requests. Sales managers will need to monitor trading activity and produce monthly reports.

To add items to the Sales List, sellers must be registered with Orinoco and be added to the Sellers List. They should be able to remove, or update their own information. Once registered, sellers should be able to post items for sale or withdraw items at any time. The system should maintain Seller Accounts and provide the Sales Manager with lists of payments to be passed by Orinoco on to sellers (after deducting a commission).

Graphical Models

Buyers should be able to view the Sales List and order items they wish to buy. To order items, the buyer must have an account, which can be created with their first order. Buyers will place required items in a “basket”, and on “move to checkout”, the order will be created and debit card payment taken. A buyer should be able to view their orders and get contact details of sellers. After an item has been ordered, the system will inform the seller, who must then ensure that the item is delivered to the buyer. If the item is unsatisfactory, buyers can return the item to the seller and ask Orinoco for a refund.

Buyers may log satisfaction feedback about their experience of Orinoco or the seller. They may also complain to Orinoco if there are problems with the seller such as poor quality, late delivery, no refund for returned items, or poor service. Orinoco managers will then deal with the sellers, and may remove them from the Sellers list.

The management of Orinoco require a system to handle the above aspects of the business. Orinoco would like the website to have a very distinctive “look and feel” in line with the Orinoco brand. The company will also need advice on hardware and software. Security of the payment system is very important. In line with the requirements of GDPR, access to seller and buyer details should be secure. The company’s accountants will want to be able to produce accounts based on trading, but this is currently outside the scope of this project. The Managing Director is also keen that the system will be accessible to visually impaired buyers.

Types of relationships between classes are shown by different types of lines linking the classes. Give one example of each type of relationship shown in the above diagram:

·name the type of relationship

·identify the two classes that are linked by the relationship

·explain the nature of the relationship.

Explain the difference between implementing the above one-many relationship between Buyer and Order in a relational database and implementing it in an object-oriented language (such as Java).

If the OOPS system described above is implemented using a Relational Database, explain THREE different ways in which the relationship between Seller, Private and Retail can be reflected in database tables, and say briefly when you would use each way.

The acronym ORM is used in system implementation. Explain what ORM stands for, what it involves and why it is necessary: