• Briefly explain requirements engineering as a process aimed at identifying the customer requirements and the constraints for its provision.

• The different stages include Inception (line of questions aiming to understand the problem, the people and their expectations, the environment and its constraints), Elicitation (through meetings with stakeholders, customers, and developers), Elaboration (developing a refined technical model e.g. Use cases, of software functions, features, and constraints), Negotiation (conflict resolution or normalizing expectation and reality), Specification, Validation, Requirements management. The aim will be to establish a good foundation for the design and construction of the software.

• Prototyping tools will play a major role in every stage, esp in respect of apps or tools within the social media context, where the business case can change as quickly as the preferences of different communities of users in terms of style, functionality, presentation, and usability.

the main entity sets are student, course, course-offering, and instructor. The entity set course-offering is a weak entity set dependent on the course.

The assumptions made are :

i)A class meets only at one particular place and time. This E-R diagram cannot model a class meeting at different places at different times.

ii)There is no guarantee that the database does not have two classes meeting at the same place and time.

FOR ER DIAGRAM DOWNLOAD THE BELOW ATTACHMENT :