Assist with these two case studies

Your analysis should consider various factors, including stakeholders involved, target audience, technology, business drivers, culture, time/schedule, resources, scope, and quality.

Please ensure that you use the APA7 referencing style while using references to support your decision-making process.

CASE STUDY 1: BUSINESS UNIT (BU) for EDU_FUNs Draw for Fun and Learn (A business unit is a logical grouping of related business activities. If an organization is structured around departments or divisions that have separate products, customers, and marketing lists, business units can be created and mapped to the organizations departments or divisions. Users can securely access data in their own business unit, but they cant access data in other business units unless they are assigned a security role from that business unit.)

EDU_FUN is an educational software development company that launched a drawing/painting software named ' Draw for Fun and Learn' in 2021 to cater to the increasing number of online students due to the COVID-19 pandemic. The software was a huge success and exceeded the company's sales projections. However, the project faced several management issues during its execution, such as undefined requirements, inadequate planning, poor project management, and random role assignment due to hasty business decisions and competition from existing products.

The project had issues ranging from ill-defined requirements, lack of planning, inadequate project management, and random role assignment due to the rush business decision and other existed competitors. Most of EDU_FUNs other products at that time were among the best available products on the market. Though the product was built in EDU_FUNs standard style, the Business Unit project needed a structure - a process framework to guide the development.

You did some research on the BU project and gathered the followings information about EDU_FUN: Work culture: The work culture at EDU_FUN at that time was informal - software engineering staff handled project execution decisions; roles were interchangeable, and projects were carried out without formal requirements documentation.

Release strategy: EDU_FUNs preferred strategy was to deliver the product in many small releases with short durations.

Time constraint: The initial project was scheduled to be delivered in six months. Focus on programming: EDU_FUNs projects at that time relied heavily on programming- build and demonstrate model. It had always worked for them in the past.

Developers and managers were not very concerned with the software architecture or process methodologies.

2:\ CASE STUDY 3: FLIGHT CONTROL SYSTEM SOFTWARE The aircraft flight control system (FCS) is a high-risk flight system that controls every aspect of an airplane operation to ensure safer, smoother flight; it consists of the flight control surfaces, cockpit controls, and the necessary mechanism to control the aircrafts direction in flight. FCS requires: Good aircraft handling properties

Low pilot workload

Model simulation or prototyping is required to analyse whether digital processing signals represent the desired implementation, to avoid any mishap during the ground or flight testing.

Backup or failover plan in case of software or hardware fault.

The system developed should be comprehensively tested for an extensive set of faults and have thorough ground-based testing. The system and its inherent functional design should be free from errors.

Additionally, FCS requires adherence to the highest level of quality standards. Any failure in the system can cause loss of aircraft and human lives; the probability of success should be very close to 100%. However, a test to prove 100 percent correctness is almost impossible. Thus, a trade-off is done by deploying many reliable, redundant artifacts, a thorough design and development process, and test-cases under all possible combinations of inputs. Redundant artifacts would be used as backup during any software fault.

The project is high risk, safety-critical, and requires zero defect deliverables along with continuous risk assessment. Thus, a spiral model is proposed as the software development process along with six sigma business management strategy.

This gives a combination of prototyping, continuous refinement, and near-zero defects. Early generations of FCS were mechanically based, so pilots had to physically steer and control the aircraft, which was limited by the physical capabilities of the pilot. Development of digital FCS would automate the process. Increase in safety as the pilot can concentrate on high-level tasks rather than routine control tasks