Software Engineering Assignment: Fishing World Case Study

Task 1: Explanation of Software Engineering Concept and SDLC

As part of the formal assessment for the programme you are required to submit a Software Engineering assignment. Please refer to your Student Handbook for full details of the programme assessment scheme and general information on preparing and submitting assignments.

After completing the module, you should be able to:

1) Identify what a system is and how a systems approach relates to Information Systems.

2) Understand the role of models in analysis and design of software systems.

3) Understand and assess software tools and technology to enhance productivity and quality of software development.

4) Create and test models of software, data and processes using object-oriented methodologies such as UML where applicable.

5) Demonstrate an understanding of a requirements analysis.

Your assignment should include: a title page containing your student number, the module name, the submission deadline and a word count; the appendices if relevant; and a reference list in Harvard format. You should address all the elements of the assignment task listed below. Please note that tutors will use the assessment criteria set out below in assessing your work. Fishing World are a leading player in the recreational and competition angling (leisure fishing) sector. Their clients are high street and online angling and sporting goods retailers, and they supply to just about every country. They are not a retail company and they do not sell direct to the public. However, they are not only wholesalers but also manufacturers with factories around the globe. Angling is one of the most popular hobbies and the company is experiencing sustained expansion.

The company headquarters are in London, United Kingdom. This is where the Chief Executive and the Board are based, along with central support functions like HR, IT, Legal etc. The CEO and Board thus constitute the senior management and are responsible for all strategic decision-making.

The company is global, large and complex and, as such, is structured along its product lines, with each product category being headed by a Product Director. Each Product Director is responsible for all aspects of that division and thus makes all tactical-level decision. They are based around the world. Each Product Director reports directly to the Senior Management back in London. There are eight Product

Directors, heading up the following product divisions:

• Rods (for sea, freshwater and game fishing)

• Reels (for sea, freshwater and game fishing)

Task 2: Critical Evaluation of Waterfall and Agile SDLC Methodologies

• Nets (keepnets and landing nets)

• Baskets and seats (what the anger actually sits on)

• Boxes and storage (tackle boxes, hook boxes, lure boxes etc.)

• Fishing line (in a wide range of breaking strains and diameters)

• Accessories (floats, weights, hooks, umbrellas etc.)

• Clothing (jackets, gloves, hats, waders and other footwear)

Within each product division there are many different factories and specialized manufacturing/testing facilities – some in urban settings, others in rural areas for field testing. Each site (factory, river, lake, etc.) is under the control of a Site Manager who is responsible for all local operational decision-making. Each Site Manager reports directly to the relevant Product Director. The date (DDMMYYYY), country of origin (UK, US, etc.) and site number (01, 02 etc.) of each product made is recorded for quality control and auditing purposes and encoded into a fixed format Product Code.

The serial number of each item and product name is also recorded. There are some examples below.

Supported by your own (fully-referenced) private research and using the above case study for specific examples, explain and describe the following:

• The software engineering concept and how it differs from programming

• The concept of the software development lifecycle (SDLC) and its stages

• Software implementation and its management via software metrics

Using your own suitable diagrams and the above case study, critically evaluate the traditional ‘waterfall’ and ‘agile’ SDLC methodologies, taking care to highlight the stages, features, strengths and weakness of each. When should each be used? What would be your recommendation to this company?

Using the supplied case study, illustrate how the Unified Modelling Language (UML) may be deployed as part of an Object-Oriented (OO) software development project. You should ensure that you clearly demonstrate the following UML features:

• Class Diagrams

• Activity Diagrams

• Sequence Diagrams

• Use Case Diagrams

Critically evaluate two implementation languages that could be used to build the planned IT system – one procedural and the other object-oriented. You should include in your response a brief overview of the following programming constructs and how your two chosen languages implement them:

• Sequence, selection & iteration

• Parameter passing and programming interfaces

• Modularity and programming ‘units’

Be sure to supply (and evidence via screenshots) your own code that demonstrates these programming features. For higher marks, you are expected to submit a fully working program but as a minimum you should submit code snippets that demonstrate the above programming constructs in each language.