DBMS Assignment 1 Vikrant Shinde (50245119) Q1. Compare Traditional SDLC Approach with RAD. Traditional SDLC (Waterfall) RAD (Rapid Application Development) • Traditional SDLC Approach involves waterfall model which is linear sequential life cycle model • The Rapid Application Development approach involves fast iterative development process with lesser planning involved. • It is best described as linear and a predictive model • It is best described as incremental and iterative model • Lower levels of productivity and flexibility because of rigidity • Higher levels of productivity and flexibility and lower time to market • The customer or the client is involved in the requirements gathering phase and in the delivery phase for user acceptance testing • The customer/client is involved in every phase of development to ease the information exchange and consistent feedback • Testing is performed after the design and coding phase is complete • Testing is performed in every iteration • Complexity of project management is considerably low • Complexity of project management is relatively higher • Suitable for long term projects • Suitable for short term projects Applications of SDLC over Agile & Vice Versa The SDLC approach is suitable for applications with lower levels of complexity and projects where there are cost constraints but are large scale. The projects which have strong prior documentation and have clearly defined stages for all the process thrive under the aegis of traditional SDLC approach. Ex. US Department of Defense Software Systems (DOD-STD-2167A) The Agile approach is suitable for applications where customer completely sure about requirements and requires continual client feedback for satisfactory development. It is suitable for applications which can broken into modules and can be worked on independently providing flexibility to the developers. Ex. Banking software with multiple modules. Q2) ER Modelling notations and applications. An Entity Relationship model is a detailed logical representation of the data for a certain company or business. In the Entity Relationship Modelling notations are used to graphically represent relationships between different entities. The different styles of
Which of the following defines a relationship in which each occurrence of data in one entity
This is a pictorial representation of the real world problem in terms of entities (which have attributes) and relations between the entities is referred to as ER diagram.
* As explained throughout this course, entity relationship modeling is a critical element of database design. If the database is not properly modeled, it is unlikely that the database will be properly developed. Using this knowledge, explain the key reasons why entity relationship modeling is important, and determine at least (1) way in which it impacts the overall development of the database.
Business Rules: In the entity-relationship data models, business rules must take into account all relationship models: one-to-many (1:M), one-to-one (1:1) and many-to-many (M:N). For a database on a school library, a restriction of having a student only allowed to borrow one book would need a 1:1 relationship.
General a database has a lot of tables and some tables are related to each other so relationship is use to make the connection between two or more tables. It is a method to avoid excessive data and to ensure the data integrity. There have three types of relationships:
Goal of analysis: GET THE REQUESTED INFORMATION TO THE CLIENT IN A TIMELY MANNER; PREVENT LOSING THE CLIENT
When it comes to the data model, there exists a relationship that has three different representations for the reason that database requires the relationship between the tables. It goes hand-in-hand with one another without the relationship the tables would have no purpose. The information cannot be repetitive in order for the each table to work and provide the specific database that is related to the information. In different ways the tables in the Huffman Trucking Fleet Truck database
Two additional pieces of information you would need to gather from the client in order to best assist him or her.
This model demonstrates the data attributes logical entities and relationships between these entities within a business function. It also helps to create the physical data model. Moreover, it shows more details while integrate business logic and business rules. This model is used to describe the domain concept and their relationship of the domain problem.
Boyde, J. (2012). A down-to-earth guide to SDLC project management: getting your system development life cycle project successfully accross the line using PMBOK-- in an adaptive way. S.l.: CreateSpace Independent Pub. Platform].
The main idea of this assignment is to develop an entity relationship diagram for a student who is willing to take various course in a semester. Entity relationship diagrams must be developed after converting the given data into the third normal form. I have learned how to dissolve a huge amount of data by using normal forms. I have also learned how to create an entity relationship diagram for a given data base. I have also learned various SQL queries and sub queries to retrieve data from the database. The final project of this course helped me to create a specific database on my own for a desired
Their Binary Types can further organize relationships: One-to-One relationships, One-to-Many relationships, and Many-to-Many relationships. The traditional model standards for ERDs call for diamonds representing relationships and rectangles representing classes. However, ERDs are loosely standardized and often look different from one another due to software such as Microsoft Access and MySql Workbench that create ERDs using proprietary applications.
Agile is a member of software development mode. Actually It is not a technique. I think not only it is a methodology, but also it is a process of development software. It will show and guide us to finish the development step by step according to the project required. However this kind of development mode is driven by human. The human will control the direction of the project.
For this project I have chosen to take a different approach to how it will be done. As studying both traditional SDLC (Waterfall) and agile approaches towards development of systems I believe that both of these methodologies have qualities of good and bad. I plan to take the best of both from each methodology, the initial phases of the Waterfall methodology provide a solid structure from which the actual build and development of the project can be started upon. From where the build and development of the actual system the process would go through an agile approach. This means that the system can be built in an iteratively where for each iteration there can be adjustments that are simply made to the system. This benefits the overall production as the development can react to changing requirements.
Computer system plays an important role in solving human problem in their daily life. There are standard steps in order to develop information system called System Development Life Cycle (SDLC). SDLC is the framework available to build a complete system. There are five phases in SDLC which are planning, analysis, design, coding, testing and maintenance (refer to Figure 1 in Appendix 1).