Please help me answering these following questions and provide at least two sour

Question

Please help me answering these following questions and provide at least two sources to support your position and examples:

1/How early or late in the Software Development Life Cycle should a team decide on the type of interface (Command-Line or Graphical User)? Explain your position.

2/How does changing the type of interface in the middle of the design or coding phase impact the flow of the project? Explain your position.

3/What is your preferred interface if you were leading a software development team project? Explain why.

Explanation / Answer

Based on my opinion, in every SDLC a team must decide to choose the type of interface they want to process the project as early as possible depending upon the resources in hand, skill set of the developers and testers, budget of the project, deadlines and meet the expectation of the client.

1.The software industry includes many different processes, for example, analysis, development, maintenance and publication of software. This industry also includes software services, such as training, documentation, and consulting.

My focus here about software development life cycle (SDLC). So, due to that different types of projects have different requirements. Therefore, it may be required to choose the SDLC phases according to the specific needs of the project. These different requirements and needs give us various software development approaches to choose from during software implementation.

Types of Software developing life cycles (SDLC)

By the SDLC a team can decide on the interface different projects have different- different types of work, complexity, requirement based on that one can decide the interface at the development stage or before that also or at the testing time or may be at the time of documentation, this all depends upon the project.

2. Based on my opinion changing the type of interface in the middle of the design or coding phase impact the flow of the project because Progress "flows" from one stage to the next, much like the waterfall in which development proceeds sequentially through a series of phases, starting with system requirements analysis and leading up to product release and maintenance. Feedback loops exist between each phase, so that as new information is uncovered or problems are discovered, it is possible to "go back" a phase and make appropriate modification. Progress "flows" from one stage to the next, much like the waterfall that gives the model its name....... it can be explain by different stages of waterfall model how it effects :

3.A decades-long goal has been to find repeatable, predictable processes or methodologies that improve productivity and quality. Some try to systematize or formalize the seemingly unruly task of writing software. Others apply project management techniques to writing software. Without project management, software projects can easily be delivered late or over budget. With large numbers of software projects not meeting their expectations in terms of functionality, cost, or delivery schedule, effective project management is proving difficult. So, if i am leading a software development team project then I will go for waterfall model because it is the best-known and oldest process is the waterfall model, where developers follow these steps in order. They state requirements, analyze them, design a solution approach, architect a software framework for that solution, develop code, test, deploy, and maintain. After each step is finished, the process proceeds to the next step.

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.