paradigms (1 Viewer)

[Kupow pow]

A glass manufacturing company is considering automating part of its production line. At the moment, 3 employees are rostered to track objects on a conveyer belt so that faulty objects are recognized and removed. The management wishes to computerize this sub-system


Which software development approach is best suited for this sub-system? Justify

 

[sunny]

What have you tried so far to answer this question? Consider all the different approaches, and determine whether it is reasonable.

 

[SamD]

I'm not sure what this question has to do with paradigms???

 

[Kupow pow]

i reckon it would be a logic paradigm

I'm not sure what this question has to do with paradigms??? [/QUOTE]
its askin what paradigm u should use

 

[sunny]

Originally posted by Kupow pow
i reckon it would be a logic paradigm

That is not a software development approach.

The logic paradigm is a programming language paradigm.

 

[Beaky]

I think he means what paradigm to choose...

I agree with SamD, very strange question to ask, I cannot see the realtionship with paradigms

My guess would be imperative... Simple IF THEN ELSE statement could answer the question (if its asking which products are faulty)

I.E

IF boxes do not meet certain requirment THEN
Throw out
ELSE proceed to next checkpoint

 

[Wild Dan Hibiki]

isnt software development approach like structured and prototype n stuff?

sorry to bring the old topic up but i wanna know wat the answer is

 

[sunny]

isnt software development approach like structured and prototype n stuff?

Yep, those ones.

 

[Wild Dan Hibiki]

so is it safe to say that this q is screwed up and shouldn't be in this forum?

 

[sunny]

I just think the original question was asked wrong - nothing to do with paradigms. If you ignore the paradigm part its a perfectly fine question to ask what software development approach is best in a given scenario.

 

[Wild Dan Hibiki]

and if it were a software development approach, wat would the answer be?

 

[SamD]

and if it were a software development approach, wat would the answer be?

I'd go for structured.

It's a very specialised module where all the requirements are known prior to development comencing. The solution will require minimal user intervention, hence most of the advantages of prototyping will not be realised. RAD is unlikely to be possible as the hardware is particular to the system so RAD tools are unlikely to be able to complete the task.

HTH
Sam

PS. This is a core question, NOT an option question.

 

[nick1048]

I'd go for structured.

It's a very specialised module where all the requirements are known prior to development comencing. The solution will require minimal user intervention, hence most of the advantages of prototyping will not be realised. RAD is unlikely to be possible as the hardware is particular to the system so RAD tools are unlikely to be able to complete the task.

HTH
Sam

PS. This is a core question, NOT an option question.

Yeah structured sounds best, perhaps a little RAD also because structured may be too costly or take too long. You'll need a faster more efficient solution.

 

[Wild Dan Hibiki]

yeah i thought RAD as well cause it makes a solution faster. but wat do i know?

 

[sunny]

Yeah structured sounds best, perhaps a little RAD also because structured may be too costly or take too long. You'll need a faster more efficient solution.

I'd have to disagree. Its very obvious when they want RAD as they'll specifically mention something about wanting the solution as soon as possible. Its true structured takes a long time and costs alot, but theres no such restrictions given in the question.

In this case I agree with Sam, but my reasoning is that given this solution is meant to be implemented into a production line for quality control (ie, mission critical) you'd want to make sure the thing works before you actually put it in for the first time. The approach that would ensure this the best is the structured approach.

 

[Wild Dan Hibiki]

good point, i have been enlightened by your post