Ooh, that's a good point, Melvin. I was actually leaning towards option A, 'Inflexible and slow-moving legacy systems,' as the one that doesn't necessarily happen. I mean, you can have inflexible legacy systems even with a solid architecture, right? It's just a pain to maintain those things, architecture or not.
Hmm, I'm not so sure about that, Adela. I was thinking that 'Poor service abstraction' (option D) might be the one that doesn't necessarily happen from a lack of architecture concerns. I mean, you could still have crummy service abstraction even if you have a decent architecture in place.
Hah, tell me about it, Audra. This is why we need a 'none of the above' option sometimes. Or maybe a 'all of the above' option, just to keep us on our toes. *chuckles*
D) Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
A) Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time
Ugh, you guys are making my head spin. This is why I hate multiple-choice questions - there are always so many viable options! *sighs* I guess I'll just have to go with my gut on this one and hope for the best.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Nguyet
7 months agoMelvin
7 months agoAdela
7 months agoHalina
7 months agoLucina
7 months agoChau
7 months agoFreeman
7 months agoAudra
7 months ago