Documente Academic
Documente Profesional
Documente Cultură
Author's initials and surname A. KHAN Students Registration Number XXXXXXXX Month and year of submission
MAY 2009
Page 1
Table of Contents
Introduction..............................................................................................3 1. Requirement Specification...................................................................3 1.1 Purpose and Scope of these Specifications ..............................................................................................................3 1.2. System Scope.................................................................................3 1.3 Operating Environment...................................................................4 1.3.1 Infrastructure............................................................................4 1.4 Functional Requirement & System Response.................................6 1.4.1 Main Concerns..........................................................................6 1.4.2 System Solution........................................................................6 1.4.3 Benefits.....................................................................................7 2. System Specification............................................................................7 2.1 Data Models....................................................................................7 2.2 Data Dictionary...............................................................................9 2.3 Process Models: DFD Diagram......................................................12 2.4 Behavioural Models: Behavioural Model for the Booking Object...13 2.4.1 Implications on the Data Structure.........................................14 2.5 Decomposition..............................................................................16 2.6 User Interface................................................................................20 2.6.2 The Database Menu Structure................................................23 3. Key Contributions...............................................................................24 3.1 Reliability of the Proposed Software Systems...............................24 3.2 Maintainability...............................................................................25 3.2.2 Metric process ........................................................................26 3.2.3 Metrics project .......................................................................26 4. Bibliography & Reference...................................................................26
Page 2
Assignment Overview Introduction Home Made Foods Catering Company is currently in the process of expansion and has sought proposals for the design of the project XTY information systems to manage the key functions of its Business. The previous systems was a manual system which often lacked a unified approach to estimate the cost of casual labour, bookings, supplier management and cancellations, thereby hampering productivity and improvement. This report would therefore outline the requirement specification of software requirements which include: functional, technical and interface specifications, which confirmed their completeness, consistency, verifiability and feasibility. The process of this specification is intended to outline the software and technical task of the requirements specification phase to the design, which identifies data, their conversion and transfer, the system functions, procedures, as well as to identify system components and communication between them. Other phases include the hierarchical decomposition of all the processes, the analysis of the key elements of the system that is necessary to establish the correctness of the system. 1. Requirement Specification
menus and its various dishes, recipes and drinks. The detailed recipes, properly defined, contribute to the automatic management of inventory and production, providing a direct interaction between the composition of the functions, menu and the management of raw materials and finished product; II. The system also offers full support to the association and the definition of the kinds of non-food, thus ensuring an integrated management of the finished product, as actually delivered to the end of the service; The collection and definition of all the information necessary to book for different types of functions and prepare the recipes and the menu is done easily and guided through a simple registration system, which allows a thorough preparation and a simple maintenance of basic information Computerization of the stock re-ordering process and other necessary modules which also includes an alert function that informs of a Minimum (Min) - Maximum (Max) level, in order that messages are generated and sent to the relevant suppliers of food and drinks when the companys stock levels goes down below a certain minimum and maximum levels; Computerization of the staff allocation process and the payment process and staff scheduling process through a process of communication between the scheduled function system and the staff roaster system to determine staff required for the planned event and payment for the casual members of staff;
III.
IV.
V.
require the use of an intranet so that the owner / CEO and key employees can all login to the existing network. The other connections would include; cables, connection boxes, and other components and connections can be made without modification to be used. At the terminal would be PC's and workstations, where each PC to be used by the different staff is connected to the Local Area Network (LAN). The company intranet would have a unique address together with the Internet address where the world is clearly responsive. This allows certain devices to be grouped, and so with rights and privileges put in place to restrict the use of certain information. 1.3.1.2 Software The basic Microsoft office tools would be most appropriate for all members of staff such as Word processing, Microsoft Excel, Microsoft PowerPoint, Microsoft Access database and Microsoft outlook. Web browsers such as Internet explorer, Firefox, Netscape Navigator and a mail client such as Microsoft outlook would suffice. 1.3.1.3 Hardware Platform & Protection Basic operating system would be the Microsoft NT server 2003, a license version or the Windows NT 4 server / 2000 for client or the licensed version of Windows 2000 professional. For the Database management system is Microsoft SQL Server 2000, as a means of protecting information from unauthorized access. The XTY information system would be operated through an intranet, which demands the operating environment as mentioned above. For the provision of intranet services is, however, this aspect should be closely followed. With the growth of the Internet boom has brought with it the growing risk of misuse or vandalism through shady of computer hackers. As a result, it is critical that the Intranet Services must ensure security against attacks by installing a recognized spyware and anti-virus programme such as Norton. Since using the XTY systems on the intranet and the internet would require the sharing of secret information which is transmitted between the sender and the employee, it is therefore critical that the procedures for system protection is strictly adhered to and that equipment is protected by restricting all unauthorised persons. 1.3.1.4 Service Providers The performance of the service provider is finally a third major area that in the discussion along with everything else. Depending on the type of services being offered would determine the level of more or less high computational power required. For uninterrupted services would therefore require the use of computer systems with high processing power, lots of memory and disk space is recommended.
Page 5
1.3.1.5 System Performance Concerns The system performance of the XTY system on the intranet service is dependent on the number of simultaneous users. Unlike the WWW public offering great many computer companies, with several thousand requests per second, is the workload in companys intranet, which is only within the office area and would therefore have very minor cases of inaccessibility. The required computing power to a server is dependent on the service offered: many applications run from the server (as a CGI application), which means that the actual work is done from the server while the client computer (workstation) only makes requests or waiting for response.
Page 6
The XTY information system shall record the initial information necessary for the management of traceability, information which, when integrated with information from bookings, allowing the reconstruction of the history of the product, from supplier to delivery.
1.4.3 Benefits
XTY information system integrates a system of complete control and transfer of all the companys product and anything else used in the running of the daily business such as plates, food, drinks and raw materials from suppliers to another and manage separate storage of goods in the long term management from raw stock, which includes the goods fast perish ability and current use. In the course features are included all those features peculiar to a typical management, such as inventory management, handling, management of inventories, etc. 2. System Specification
Page 7
Page 8
Amount Deposited Type Description/Purpo se: Usage Range Specification (BNF) Balance Amount
Page 9
Due Type Description/Purpo se: Usage Range Specification (BNF) Customer Phone Type Description/Purpo se: Usage Range Specification (BNF) Extras Type Description/Purpo se: Usage Range Specification (BNF) Menu Starter Type Description/Purpo se: Usage Range Specification (BNF)
Number This is the final amount that is paid by the customer after the function. This clears the customer of any further debt owed as the booking is finally done away with once the balance amount has been paid 0~999999 Balance now due => {Digit}* Digit => [0|1|2|9]
String Telephone or mobile number of the customer. Display the customers information None Telephone number of the customer=> {Digit} {6} Digit => [0|1|2|9] String This is an instance of where the customer selects other special requirements of the customer has deliberately chosen a couple of other items not in the standard menu. Used for order extra portions of food Drinks Other extras None B-EID{Digit}{6} Digit => [0|1|2|9] String This consist of the main starter which is found in the 10 standard menus is an instance of where the customer selects it either as the starter for a wedding, parties or just a picnic. Used for order extra portions of food Drinks Other extras None B-EID{Digit}{6} Digit => [0|1|2|9]
Page 10
Page 11
Page 12
Page 13
Page 14
Page 15
2.5 Decomposition
Page 17
Page 18
Page 19
Page 20
Page 21
Can allocate a description of the field where required, to give additional information The data type for each field, i.e. whether it holds a number or a text field. Can be crucial for validation
Can change additional information for the data type, e.g. field length from 20 to 30.
the
Page 23
main menu, form menu and report menu, all are interlinked and allows navigation through the system.
The Main Menu (Title Slide appears on screen once the system has been opened). The main menu appears on screen automatically as an autoexec macro was implemented and recorded. The main menu has links to both additional menus i.e. the form and report menus. The form and report menus are interlinked with each other and both link back to the main menu. Features On All Menus I. II. III. IV. V. All have the same background layout, and this shows consistency between the menus. The clipart picture is shown all the menus, links to the video/film theme. All the menus have buttons, depending on the menu features the buttons change accordingly. All the menu titles are in the Verdana font style, size 20 bold, and so differentiate from the main title heading. All title headings are in the Verdana font style, size 18 bold, also have an indented shadow border which highlights the main title of the menu.
3. Key Contributions
Page 24
Defects in any of the components, both hardware and software components This system has not been adequately tested so on that basis I would recommend that adequate testing be carried out by the users. One of the main concerns for this system, is the Software and reliability issue. Britton and Doake (1996) states that reliability is the key Criterion for acceptance of a System with the user. This applies to this system as well as adequate testing has not been carried out on the Standard software packages. For the user the main concern will be the frequent failures of Software products and technical devices in its environment. According to Britton and Doake (1996), under reliability is the ability of a system or component to perform to expectation based on its required function under specified conditions over a specified period of time to execute, (Britton and Doake, 1996). In discussing the reliability of the software developed, the failure rate plays an important role. In many practical cases of the case in which the failure rate to be constant over the observation time can be adopted.
3.2 Maintainability
We would recommend the need to include software metrics as a form of ensuring that it is able to meet the user requirements. Kan (2002) states that there are a number of features that should accompany effective software metrics. These characteristics are: Simple and easy to calculate, (Kan, 2002) Empirically and intuitively persuasive, (Kan, 2002) Consistent and objective, (Kan, 2002) Consisting of the use of units and size, (Kan, 2002) Independent of programming language, (Kan, 2002) Effective feedback mechanism for quality, (Kan, 2002) Although most software metrics satisfy the above characteristics, some of the commonly used metrics fail to fulfil one or two, (Kan, 2002). Maintainability metrics cannot measure the cost of making a particular change to the system software, but that measure aspects of the complexity and quality of programs as there is a high correlation between the complexity and maintainability (a more complex lower maintainability) and between the quality and maintainability (the higher quality higher maintainability - and vice versa -). There are ways to measure the maintainability for all software components that are or will be undergoing maintenance code, user documentation, analysis or design documents, etc.
Page 25
Page 26