Software Engineering Exam - Study Notes

Software engineering is a systematic approach that focuses on the design, development, and maintenance of software systems. It involves applying engineering principles and practices to software development to ensure quality, reliability, and efficiency.

SRS stands for Software Requirements Specification. It is a document that outlines the detailed requirements for a software system. It describes what the software should do, how it should behave, and the constraints it must adhere to.

1. Honesty and integrity in software development practices.
2. Respect for intellectual property rights and proper attribution of work.
3. Data privacy and security, ensuring responsible handling of user data.
4. Professional competence and commitment to continuous learning.

<p>Software process activities include requirements gathering, analysis, design, implementation, testing, deployment, and maintenance. These activities represent the steps involved in building and managing software.</p> Signup and view all the answers

<p>The waterfall model is a linear, sequential approach to software development. It progresses through distinct phases such as requirements, design, implementation, testing, and deployment, each with its own deliverables.</p> Signup and view all the answers

<p>Architectural design focuses on defining the high-level structure and organization of a software system. It outlines the major components, their interactions, and how they will work together to achieve the system's goals.</p> Signup and view all the answers

<p>Web applications are used for a wide range of purposes, including e-commerce, social media, online banking, content management systems, and much more. They provide access to services and information over the internet, enabling user interaction and data exchange.</p> Signup and view all the answers

<p>Some key principles of user interface design include:</p> <ol> <li>Consistency - Maintain a consistent design across the application for ease of use.</li> <li>Clarity - Use clear and concise language and visuals for easy understanding.</li> <li>Efficiency - Provide intuitive and efficient ways for users to accomplish their tasks.</li> <li>Feedback - Provide timely feedback to users to confirm their actions and guide them through the process.</li> <li>Forgiveness - Design the interface to minimize errors and provide recovery mechanisms if mistakes are made.</li> </ol> Signup and view all the answers

<p>Software quality refers to the overall excellence and performance of a software system. It encompasses factors like functionality, reliability, usability, performance, maintainability, and security.</p> Signup and view all the answers

<p>White-box testing, also known as structural testing, is a software testing technique that examines the internal logic and code structure of a system. It involves testing the system's code pathways and verifying the correctness of individual components, such as functions, algorithms, and data structures.</p> Signup and view all the answers

<p>Unit testing is a software testing technique that focuses on testing individual units or components of a system in isolation. It involves writing specific test cases to verify the functionality and logic of each unit, ensuring that it produces the expected outputs for given inputs.</p> Signup and view all the answers

<p>A software requirements document (SRD) is a comprehensive document that outlines the detailed specifications for a software system. It encompasses both functional and non-functional requirements, detailing what the system should do, how it should behave, and the constraints it must adhere to. It defines the scope, features, performance, and usability of the system. It is a vital tool for communication between stakeholders, developers, and testers.</p> Signup and view all the answers

<p>Scrum is an agile software development framework that emphasizes iterative and incremental development. It uses short, time-boxed cycles called sprints to build and improve software through collaborative efforts. Each sprint is typically two to four weeks long, and it follows a structured process.</p> Signup and view all the answers

<p>In a layered architecture, software components are organized into distinct layers, each responsible for specific functionalities. Typically, layers are arranged in a hierarchical structure, with lower layers providing services to upper layers. This allows for modularity, separation of concerns, and reduced coupling between components. For example:</p> <ol> <li> <strong>Presentation Layer:</strong> Responsible for user interactions, displaying information, and handling user inputs.</li> <li> <strong>Business Logic Layer:</strong> Contains core application logic, business rules, and data validation.</li> <li> <strong>Data Access Layer:</strong> Interfaces with data sources such as databases or file systems.</li> <li> <strong>Database Layer:</strong> Manages data storage and retrieval.<br /> This layered architecture allows for changes to one layer without impacting others.</li> </ol> <p><strong>Diagram:</strong></p> <pre><code> [Presentation Layer] / \ [Business Logic Layer] [Business Logic Layer] / \ / \ [Data Access Layer] [Data Access Layer] | [Database Layer] </code></pre> Signup and view all the answers

<p>The Golden Rules of User Interface Design are a set of guidelines that promote effective and user-friendly interface design. They aim to make software interfaces intuitive, consistent, and easy to use. Key rules include:</p> <ol> <li> <strong>Consistency:</strong> Employ consistent terminology, icons, and layout throughout the interface. This reduces user confusion and learning curve.</li> <li> <strong>Minimize User Memory Load:</strong> Design the interface to minimize the user's need to remember information from one point to another. Use clear labels, prompts, and contextual help to facilitate user navigation.</li> <li> <strong>Feedback:</strong> Provide immediate feedback to users about their actions and system status. This ensures users feel in control and understand the system's responses.</li> <li> <strong>Clarity:</strong> Use clear and concise language in messages, instructions, and prompts. Avoid technical jargon or overly complex terms.</li> <li> <strong>Error Prevention:</strong> Design the interface to prevent the user from making errors, such as validation input fields or providing clear guidance for common errors.</li> <li> <strong>Flexibility:</strong> Allow users to tailor the interface to their preferences and needs. Offer customization options, such as theme settings, language preferences, or keyboard shortcuts.</li> <li> <strong>Efficiency:</strong> Optimize the interface for speed and efficiency. Provide quick access to frequently used functions. Use shortcuts and keyboard combinations to streamline tasks.</li> </ol> Signup and view all the answers

<p>Black box testing is a software testing technique that focuses on examining the external behavior of a system without looking at the internal code logic. It involves testing the system's functionality and usability, ensuring it produces the expected outputs for given inputs. This approach is based on the idea of treating the software system as a black box, where the internal workings are hidden from the tester.</p> Signup and view all the answers

<p>The incremental software process model is an iterative approach that breaks down software development into smaller increments or iterations. Each increment delivers a working, but potentially incomplete, version of the software. It allows for early feedback from users and stakeholders, providing opportunities for adjustments and improvements throughout the development process.</p> <p><strong>Merits of Incremental Model:</strong></p> <ul> <li>Early delivery of working software, allowing for feedback and adjustments.</li> <li>Reduced risk of large project failures.</li> <li>Easier to manage and adapt to changing requirements.</li> <li>More flexible and responsive to user needs.</li> </ul> <p><strong>Demerits of Incremental Model:</strong></p> <ul> <li>Difficulty in planning and estimating the overall project timeline.</li> <li>Requires careful planning and coordination to ensure increments integrate smoothly.</li> <li>May not be suitable for highly complex or critical systems where all requirements need to be defined upfront.</li> </ul> Signup and view all the answers

<p>A sequential diagram, also known as a sequence diagram, is a type of UML (Unified Modeling Language) diagram that shows the interactions between objects in a system over time, specifically focusing on the order of messages exchanged between them. It provides a visual representation of the interactions between objects in a sequence, helping to understand the flow of communication and the execution of operations within the system.</p> <p><strong>Example: Ordering a pizza</strong> A sequential diagram depicting the interactions between a customer, a cashier, and a pizza chef at a pizza restaurant would show:</p> <ol> <li>The customer sends a message to the cashier to order a pizza.</li> <li>The cashier receives the message and sends a message to the pizza chef to prepare the pizza.</li> <li>The pizza chef receives the message and prepares the pizza.</li> <li>The pizza chef sends a message to the cashier indicating the pizza is ready.</li> <li>The cashier sends a message back to the customer notifying them that the pizza is ready.</li> </ol> <p>This visual representation helps to understand how the different objects in the system interact and how the order is fulfilled.</p> Signup and view all the answers

<p>Functional requirements define the specific behaviors and functionalities that a software system must provide. They specify what the software should do, including the actions it should perform, the data it should process, and the outputs it should produce. They answer the question of what the system is expected to accomplish.</p> <p>Examples of functional requirements include:</p> <ul> <li>The system should allow users to create new accounts.</li> <li>The system should calculate the total cost of an order based on selected items.</li> <li>The system should generate reports on sales performance.</li> </ul> Signup and view all the answers

<p>Mobile interface design principles focus on creating user-friendly and engaging interfaces specifically for mobile devices. They consider the unique constraints and capabilities of these devices, such as smaller screen sizes, touch input, and limited processing power.</p> <p>Key principles include:</p> <ol> <li> <strong>Simplicity:</strong> Keep the interface clean, uncluttered, and easy to navigate. Avoid excessive text, complex layouts, or overwhelming features.</li> <li> <strong>Touch-Friendly Interactions:</strong> Design interactions that are intuitive and responsive to touch input. Use large buttons, clear gestures, and a minimal number of taps to complete tasks.</li> <li> <strong>Visual Hierarchy:</strong> Employ visual cues and design elements to guide users through the interface. Use clear typography, color contrast, and visual emphasis to highlight important elements.</li> <li> <strong>Performance Optimization:</strong> Ensure the mobile app loads quickly, responds smoothly to user interactions, and consumes minimal battery life. Optimize images, reduce code size, and consider device capabilities.</li> <li> <strong>Context Awareness:</strong> Design the interface to adapt to the context of use. For example, consider the user's location, time, or network connection to provide relevant information or features.</li> </ol> Signup and view all the answers