System Development Requirements and Constraints Y/505/4634
Total Page:16
File Type:pdf, Size:1020Kb
Cambridge TECHNICALS OCR LEVEL 3 CAMBRIDGE TECHNICAL CERTIFICATE/DIPLOMA IN IT SYSTEM DEVELOPMENT REQUIREMENTS AND CONSTRAINTS Y/505/4634 LEVEL 3 UNIT 35 GUIDED LEARNING HOURS: 60 UNIT CREDIT VALUE: 10 SYSTEM DEVELOPMENT REQUIREMENTS AND CONSTRAINTS Y/505/4634 LEVEL 3 UNIT 35 AIM AND PURPOSE OF THE UNIT Before developing a system, careful consideration must be given to the systems software and hardware to be used. There is a significant number of different operating systems and hardware configurations which support system development and the compatibility of these is essential. The purpose of this unit is to provide learners with detailed knowledge of which systems software and hardware are appropriate when developing different systems including basic, complex and multi-purpose systems. Learners will understand the constraints and compatibility issues that may occur during the system development process and how to resolve these, including the use of diagnostic systems software and tools. www.ocr.org.uk 2 System development requirements and constraints Level 3 Unit 35 ASSESSMENT AND GRADING CRITERIA Learning Outcome (LO) Pass Merit Distinction The assessment criteria are To achieve a merit the To achieve a distinction the the pass requirements for evidence must show that, in evidence must show that, this unit. addition to the pass criteria, in addition to the pass and the learner is able to: merit criteria, the learner is The learner will: The learner can: able to: 1 Know hardware P1 describe hardware M1 describe hardware D1 evaluate hardware methodologies and methodologies and methodologies and methodologies and systems software used systems software systems software systems software to support system used to support used to support used to support development development of a basic development of a development of a system complex system complex system. 2 Understand systems P2 explain systems software and software constraints hardware constraints associated with system associated with system development development P3 explain hardware constraints associated with system development 3 Understand solutions to P4 explain how systems M2 explain why cross- systems software and software constraints platform software hardware constraints can be resolved development is associated with system beneficial development P5 explain how systems M3 explain how a hardware hardware constraints compatibility list can can be resolved reduce constraints encountered during system development Be able to use diagnostic P6 use a diagnostic tool D2 evaluate the tools to resolve systems to resolve systems effectiveness of a software and hardware software and hardware diagnostic tool when problems problems resolving systems software and hardware problems 3 TEACHING CONTENT The unit content describes what has to be taught to ensure that learners are able to access the highest grade. Anything which follows an i.e. details what must be taught as part of that area of content. Anything which follows an e.g. is illustrative, it should be noted that where e.g. is used, learners must know and be able to apply relevant examples to their work though these do not need to be the same ones specified in the unit content. LO1: Know hardware methodologies and systems • desktop computers and laptops (e.g. Linux, Mac OS X, software used to support system development Windows) Computer types: • tablets and phones (e.g. Android, iOS, Windows Phone) • (e.g. supercomputers, mainframes, servers, computer languages supported by operating systems: workstations, desktop computers, laptop computers, (e.g. C++ - Android, Mac OS X, Linux, Solaris, Windows; games console, tablets, mobile phones, embedded Java - Android, Mac OS X, Linux, Solaris, Windows; systems) Python – Android, Mac OS X, Linux, Solaris, Windows; Scratch - Windows, Mac OS X; Visual Basic - Windows) Hardware methodologies: software development tools: • processor family (e.g. Intel, PowerPC, AMD) • Assembler • processor performance (e.g. speed, efficiency) • Compiler: (e.g. C, C++, C#, Java) • hard disk capacity • Interpreter: (e.g. BASIC, LISP, Python, Ruby) • temporary storage (e.g. RAM) • Integrated Development Tools: (e.g. Microsoft Visual • motherboard Studio, Xcode, Eclipse, BlueJ, NetBeans) • input/output devices • Software Development Kits/Software Developer’s Kits (e.g. Window’s Phone SDK, QuickTime Mac OS, Android • memory cards SDK, iOS SDK for ipad) • graphics cards • Application Development Software: (e.g. iOS Developer, • video cards Flex, Adobe Flash Builder, Blend) • sound cards Evaluation • screen (e.g. size, resolution) • functionality (e.g. does the hardware and software solve • communication devices identified outcomes of the system, are they efficient, any issues identified) Systems software • compatibility issues (e.g. computer type and hardware Computer system types: methodology, computer system and operating system, • basic systems (e.g. desktop computers, laptop computers) computer language and operating system, software • complex systems (e.g. tablets) development tools and computer system, any issues identified) • multi-purpose platforms (e.g. games console, mobile phones, embedded systems) • reliability (e.g. are the outcomes of the system accurate) • usability (e.g. ease of use, user friendliness, help and Operating system types: (e.g. Graphical User Interface support available, any issues identified) (GUI), , multi-user, multi-processing, multi-threading) • security (e.g. does the hardware and software used ensure Operating systems for computer systems: no issues with security, any issues identified) • large computer systems (e.g. Solaris, Unix, z/OS) • maintainability (e.g. is the hardware and software easily www.ocr.org.uk 4 System development requirements and constraints Level 3 Unit 35 modifiable/upgradable, any issues identified) • disadvantages of buying (e.g. cost, incompatibility, interoperability) LO2: Understand systems software and hardware • advantages of building (e.g. specific requirements, constraints associated with system development portability) Systems software constraints • disadvantages of building (e.g. time, inaccuracies) • outdated systems software versions Download a software patch • incompatibility between software (e.g. operating system • advantages of downloading a software patch (e.g. free) and programming language) • disadvantages of downloading a software patch (e.g. • limited memory can contain errors, can be out-of-date/become out-of-date • limited storage quickly) • registry issues Programming toolkits and environments (e.g. Mozilla • issues with device drivers Application Framework, GeneXus, Real Studio) • accessibility (e.g. screen resolution) Cross-platform programming (e.g. Java, Python, Ruby) • lack of technical skills Backward compatibility (e.g. Windows, Mac) • cost (e.g. financial, time) Diagnostic tools (e.g. Pc-Check®, PC Inspector, QuickTech IA, QuickTech Windows, QuickTech PRO, QuickTech xA, Hardware constraints BMC, IBM Tivoli) • outdated hardware specifications • de-compilers • incompatibility between hardware and systems • system checking/testing software Hardware solutions • proprietary hardware Upgrade hardware (e.g. add additional memory, • hardware restrictions increase hard disk storage capacity, replace cards) • accessibility (e.g. screen size) Hardware compatibility list • interoperability between hardware components • (e.g. Linux, Mac, Windows, Oracle Linux, VMWARE) • lack of technical skills • cost (e.g. financial, time) Support/references LO3 Understand solutions to systems software • manufacturer’s documentation (e.g. printed manuals, and hardware constraints associated with system on-line manuals) development • manufacturer’s website (FAQ, help guides) Systems Software solutions • web pages, Upgrade software • web forums Buy or build: • specialist computer magazines • off-the-shelf:(e.g. Mac, Windows) • computer journals • bespoke: (e.g. device drivers) • training materials • advantages of buying (e.g. quality, effectiveness, • trouble-shooting guides availability) 5 LO4 Be able to use diagnostic tools to resolve systems software and hardware problems Diagnostic tools (e.g. Pc-Check®, PC Inspector, QuickTech IA, QuickTech Windows, QuickTech PRO, QuickTech xA, BMC, IBM Tivoli) Evaluation • usability (e.g. ease of use, what help and support does it offer the user) • functionability (e.g. general maintainance features, management/diagnostics features, repair and recovery features, optimization features, security features) • acceptability (e.g. what operating system software does it support i.e. is it Windows compatible, Mac compatible, etc.) www.ocr.org.uk 6 System development requirements and constraints Level 3 Unit 35 DELIVERY GUIDANCE Learners should then be able to evaluate the hardware Know hardware methodologies and systems software methodologies and systems software that can be used to used to support system development support development of a complex system. They should be Learners should be taught about the different types of able to evaluate aspects such as functionaility, for example, operating systems, the types of computer systems that they does the hardware and software solve identified outcomes support, and the platforms with which they are associated. of the system, are they efficient and whether any issues This could be delivered through lectures, practical exercises have been identified. They need to evaluate compatibility and research. Features and limitations of each could be issues, such as computer type