Which one model is the best ?

Started by electra, 12-10-2011, 08:33:06

Previous topic - Next topic

electraTopic starter

Which one process model of software engineering is the best for database applications?
Reliable hosting? try HOSTGATOR and WEBHOSTINGHUB.
  •  


allricjohnson

Its always good to use the traditional waterfall model.....but since the requirements keep on changing i think u should see Spiral process model. Thank you.
River Delta India is an USA and India based Internet Marketing Services providing Company.
  •  


damponting44

The company delivers cost-effective solutions that maximize their clients' money making potential through increased web exposure and brand awareness. Their services include SEO, social media and website services. Boostability also works with partners that offer their white-labeled SEO, social media, and website building services to their small business clients.   

saravanan28

#3
There is no one-size-fits-all answer to the question of which process model is best for database applications in software engineering. The choice of process model depends on various factors such as project requirements, team size, timeline, and development methodology preferences.

That being said, some commonly used process models for database applications include the Waterfall model, Agile methodologies like Scrum or Kanban, and Incremental models. Each of these models has its own strengths and weaknesses, so it's important to evaluate them based on your specific project needs.

For example, the Waterfall model can be suitable for well-defined and straightforward database projects where all requirements are known upfront. On the other hand, Agile methodologies might be more appropriate if the project requires flexibility and iterative development.

Ultimately, it is advisable to assess your specific requirements and constraints before deciding on the most suitable process model for your database application.

models commonly used in software engineering that can be suitable for database applications:

1. Spiral Model: The Spiral model is a risk-driven model that combines elements of both iterative and waterfall models. It involves multiple iterations and emphasizes risk analysis and mitigation throughout the development process. This model is beneficial for large and complex database applications where risks need to be identified and addressed early on.

2. Rapid Application Development (RAD): RAD is an iterative and incremental model that focuses on prototyping and quick development cycles. It emphasizes user feedback and involvement throughout the development process. RAD can be useful for database applications that require fast delivery and frequent iterations to accommodate changing requirements.

3. DevOps: DevOps is not just a process model but a philosophy that integrates development and operations teams to foster collaboration, automation, and continuous delivery. DevOps can be applicable to database applications that require seamless deployment, monitoring, and management of database systems.

4. Feature-Driven Development (FDD): FDD is an iterative and incremental process model that focuses on designing and building features in small, manageable increments. It emphasizes domain object modeling, feature development, and regular client involvement. FDD can be suitable for database applications with well-defined features that can be developed independently.
  •  

dark404

The organization conveys financially savvy arrangements that boost their clients' lucrative potential through expanded web openness and brand mindfulness. Their administrations incorporate Web optimization, online entertainment and site administrations. Boostability likewise works with accomplices that offer their white-named Search engine optimization, online entertainment, and site building administrations to their private venture clients.


f1dark

Oracle is an object relational database management system, which allows objects to be stored in tables, in a manner similar to numbers and words being stored in an RDBMS system.

The only interface available between end users and an RDBMS is Structured Query Language (SQL). All other applications and tools that users utilize to interact with the RDBMS act as translators/interpreters. These tools generate SQL commands based on a user's request and pass the generated SQL commands on to the RDBMS.