MANAGING A DATABASE PROJECT
A consulting project involved a credit card "bottom feeder" (let's call it Credit Wonder). This company bought credit card accounts that were written off as uncollectable debts by major banks. Credit Wonder would buy the write-off accounts for 1 or 2 percent of their value and then would call the owners of the writ ten off accounts and "offer a deal" to the credit card account holders. Credit Wonder wanted a database for these accounts. Legally, it did own them and so could contact the people who had owed the money-but as prescribed in credit law. For example, Credit Wonder could call only during certain hours and no more than once a week, and they had to speak to the actual account holder. Any amount collected over the 1 to 2 percent of the original debt would be considered a gain. In its database, Credit Wonder wanted a history of what settlement was offered, the date the account holder was contacted, and additional notes.
QUESTIONS:
1. How might a systems analyst manage such a system project?
2. Who would the systems analyst need to interview to get the system requirements?
3. How would a database analyst help in structuring the database requirements?