Assignment Semester 2 IT Skills(WBL version) CE

Transcription

1 Staffordshire University Assignment Semester 2 IT Skills(WBL version) CE Hand In Date Part one 12th March 2010 Demonstration of Part two week commencing 3 rd May 2010

2 Contents Your Task is to do the following:... 4 Part Part 2 Prototype... 5 Part 1 Marking Scheme... 6 Part 2 Marking Scheme P age

3 Learning Outcomes 2) COMPARE AND CONTRAST THE PURPOSE, STRUCTURE AND SCOPE OF A TRADITIONAL METHODOLOGY Knowledge & Understanding 3) IDENTIFY THE FRAMEWORK OF ACTIVITIES ASSOCIATED WITH A METHODOLOGY AND DESCRIBE HOW THE TECHNIQUES ARE USED TOGETHER TO DEVELOP A SYSTEM. Problem Solving 4). DEVELOP A SIMPLE PROTOTYPE, WITH A SUITABLE INTERFACE, FROM CONCEPTION THROUGH TO IMPLEMETATION Application 5) DEMONSTRATE, APPLY AND DOCUMENT, TO THE APPROPRIATE STANDARDS, THE KEY TECHNIQUES OF ANALYSIS AND DESIGN Communication Reflection The Scenario: A small electrical shop in your town has just been sold and the new owners want to expand the shop into new markets so they have decided to sell Mobile phones from Pay as you go to monthly phone contracts. As the shop was only small and was previously owned by an elderly couple no computer system was ever used, just pieces of paper and sales books. The records that the owners kept would sometimes get mislaid i.e. new customers, old customer s goods purchased and so on. It was difficult to tell customers about offers and promotions that the shop had on offer as the owners spent less and less time at the shop before its eventual sale. The new shop owners require a new computer system for the business but at the moment they have decided only to have one built for the sale of the mobile phones as they have never used a computer system before. The system must be able to do the following Show what phones are in stock, make, module, colour and features What phones are on order? Show different talk plans including pay as you go. Show special offers. List customer details e.g. the system must be able to record all new customers and existing customer details and which phone and which contract they are on. 3 P age

4 Your Task is to do the following: You are required to design and create a Microsoft Access database containing information for the company to use in their business You will use the case study above. You will apply the techniques of data and process modelling to determine the required design. You must use a CASE tool containing appropriate facilities for checking diagrams. The one to be used is Select SSADM Professional or equivalent. You should remember that the system you design must be capable of providing the details required for the queries that you might need. Hand In Date Part one 12th March 2010 Demonstration of Part two not later than week commencing 3 rd May 2010 Part 1 Report (65%) 1. Write a short paragraph identifying the aim of the system (2%) 2. Identify the requirements of the company (5%) 3. A Use Case model for the system including a use case description for all of the use cases shown on the diagram (8%) 4. A Process model (set of Data Flow Diagrams) including: a. Context Diagram (2%) b. Level 1 DFD (2%) c. Decomposition of one level 1 process only to an appropriate level (10%) One example of each of the following: Process description for one elementary process (2%) Data flow description (2%) Data store description (1%) External Entity Description (1%) 5. An appropriately normalised entity relationship diagram (15%) a. An attribute list for each entity, including the identification of primary and foreign keys (5%) b. Details of the tables and relations that are required, in the development of the prototype, to implement the data model. A commentary on the design and implementation decisions and compromises that were made should be included. (5%) 6. The work submitted should be professionally presented (5%) 4 P age

5 Part 2 Prototype and demo (35%) 7. A individual demonstration of a prototype of the following elements of the proposed system: It is required that a prototype, built in Microsoft Access, is tested and demonstrated. The prototype will include the following : A form based on a query of your choice A selection of reports of your own choice. The form and the reports should be based on the requirements identified in Part One of the assignment. You will need to populate the tables in your database with sufficient test data to demonstrate the functionality of your form and reports. The demonstration is to take place not later than Friday 7 th May You should bring with you a copy of your database on CD, clearly labelled, and hand that in at the end of the demonstration. 5 P age

6 Part 1 Marking Scheme Area Marks Guidance Remarks Statement of the aim of the current system (Max 2) >1½ For a shortish paragraph that succinctly describes what the Phone Company and their "systems" seek to achieve 1-1½ For a statement that describes what the Phone Company and their system seek to achieve but is couched at the wrong level of detail or a succinct statement that does not encapsulate the whole. <1 Does not satisfy the above criteria Requirements list (Max 5) 3> List of requirements complete and well documented using formal templates 2-3 Most requirements listed but lacking formal documentation <2 Does not satisfy the above criteria Use Case Model including descriptions for all of the use cases shown on the diagram (Max 8) Levelled set of data flow diagrams including one Process description Data flow description Data store description External Entity Description (Max 20) 6> Use Cases chosen meet all aspects of user requirements and are described in detail 5-6 There is a good correspondence between the diagram and the descriptions 4-5 One use case has a detailed description that broadly meets the users requirements for that area 3-4 Use Case model provided shows some useful contribution to the documenting of user requirements <3 Does not satisfy the above criteria 14 > For a complete set of levelled DFD s and supporting text that demonstrate excellent understanding of the technique, correct use of symbols and represents the situation at the Phone Company For a complete set of levelled DFDs that demonstrate good understanding of the technique. Symbols will be used correctly in the vast majority of cases. The supporting text may not be complete or may be lacking appropriate detail. Some minor areas of the Phone Company situation may not be well covered For a set of DFDs that demonstrate some understanding of the technique. Most major areas of the Phone Company operations will be modelled. Symbols will be used correctly in the most cases. The supporting text is likely to be skimpy For some DFDs that may or may not be levelled. Little understanding of the technique. Incorrect use of symbols. <8 Does not satisfy the above criteria Hand-drawn diagrams are not acceptable SELECT SSADM CASE tool or eaquivalentmu st be used Entity relationship model Entity relationship diagram Entity descriptions Attribute list including primary and foreign keys (Max 25) 18> For an ERM that demonstrates excellent understanding of the technique. The structure to support all areas of the Phone Company operations will be modelled - exclusions will be documented. Symbols will be used correctly. All relations will show degree, nature and optionality. Attribute lists will be complete and keys will be identified correctly. Descriptions will be fitting ½ For an ERM that demonstrates good understanding of the technique. The structure to support all major areas of the Phone Company operations will be modelled - exclusions may be documented. Symbols will be used correctly. Most relations will show degree, nature and optionality. Attribute lists will generally be complete and keys will be identified correctly. Descriptions will be fitting ½ For an ERM that demonstrates some understanding of the technique. The structure to support most areas of the Phone Company operations will be modelled. Most symbols will be used correctly. Relations may show degree, nature and optionality. Attribute lists may not be complete and keys may not be identified correctly. Descriptions will be skimpy if existing at all ½ For an ERM that demonstrates little understanding of the technique. The structure to support few areas of the Phone Company operations will be modelled or may be modelled in a way that simply will not work at all. Symbols may be used incorrectly. Relations will show none of degree, nature and optionality. Attribute lists will not be complete and keys may not be identified. Descriptions are unlikely to exist. <10 Does not satisfy the above criteria Hand-drawn diagrams are not acceptable SELECT SSADM CASE tool must be used Presentation of report 3½ > Convincingly professional report that is fully compliant with faculty standards 6 P age

7 Area Marks Guidance Remarks (max 5) 1-3½ For a fairly well presented report that adheres to faculty standards but evidence of meetings is rather skimpy. <1 For a scruffy, unstructured, illegible, hand-written mess Part 2 Marking Scheme Implementation (Max 35) >25 The implementation will work in full and could be used in a real world application meeting most of the major requirements of the user. Queries work and are presented in a suitable form to provide what is required by user. Many features of DBMS have been used to provide users with a clear and simple method of data entry Queries provide the information required. Suitable navigation is provided. Some validation rules have been used for data entry. Suitable test data has been entered for all queries ½ Referential integrity is provided in at least one place. At least one sub-form has been used in appropriate fashion. Some features have been used to provide simple data input. Practical skills demonstrated will be satisfactory although some elements of the implementation may not have full functionality ½ Most tables represent entities in the design. Primary and foreign keys have been identified in all tables. Suitable data types have been identified for most fields. Test data may be insufficient. At least one query works with suitable chosen criteria. <12 May not support the needs of the company or some of the queries may not work. The implementation may be minimal. Primary keys have been identified in at least one table. Suitable data types have been chosen for some fields. At lease one suitable relationship has been established between 2 tables. 7 P age